You can specify settings that Output uses for caching,
which can optimize the performance of your LiveCycle environment.
To access these settings, in Administration Console, click Services
> LiveCycle Output 11.
Note: Disk requirements for the cache should be equal
to the repository.
Specifying global cache settingsThe settings in the Global Cache Settings area affect
all types of caches. If you change either of these settings, restart
the Output service for the change to take effect. To restart this
service, either use Workbench or see Start or stop the services associated with LiveCycle modules for
instructions.
- Max Cache Document Size (KB):
- The maximum size, in kilobytes, of a form design or other
resource that can be stored in any in-memory cache. This is a global
setting that applies to all in-memory caches. If resource is larger
than this value, it is not cached in memory. The default value is 1024 kilobytes.
This setting does not affect the disk cache.
- Form Rendering Cache Enabled:
- By default, this option is selected, which means that rendered
forms are cached for subsequent retrieval. This setting has little
effect on the performance of the Output service because it does
not cache non-interactive documents. This option does have an effect
when you use the Output service to non-interactive documents that
are rendered on the client.
Caching form designsWhen the Output service receives a render request, it retrieves
the form design from the repository or from an HTTP source and caches
it. This caching improves performance because for subsequent render
requests, the Output service retrieves the form design from the
cache instead of from the repository.
The Output service always caches form designs on disk. If form
designs are stored on the server, those files are considered the
disk cache. The Output service also caches form designs in memory,
according to the setting in the In Memory Template Cache area.
If you change any of these settings, restart the Output service
for the change to take effect. To restart this service, either use
Workbench or see Start or stop the services associated with LiveCycle modules for
instructions.
- Template Configuration Cache Size:
- The maximum number of template configuration objects to keep
in memory. The default value is 100. It is recommended that you
set this value greater than or equal to the Template Cache Size value.
This setting does not affect the disk cache.
- Template Cache Size:
- The maximum number of template content objects to keep in
memory. The default value is 100. This setting does not affect the
disk cache.
- Enabled:
- By default, this check box is selected, meaning that form
templates are cached in memory. When this option is not selected,
form templates are cached only on disk.
Caching fragments and imagesThe Output service caches fragments and images use in form
designs on disk. This improves performance because the fragments
and images are only read from the repository on the first request.
Then on subsequent requests, the Output service reads fragments
and images from the disk cache. Fragments and images are cached
only on disk, and not in memory.
You can use the following settings to control the on-disk caching
of fragments and images. These settings are located in the Template Resource Cache Settings area:
- Resource Caching
- Select one of the following options from the list:
- Enabled for fragments and images:
- The Output service caches fragments and images. This is the
default option.
- Enabled for fragments:
- The Output service caches fragments, but not images.
- Disabled:
- The Output service does not cache fragments or images.
- Cleanup Interval (Seconds):
- Specifies how often the Output service removes old invalid
cache files. The Output service does not remove valid cache files.
If you change the cleanup interval, restart the Output service for
the change to take effect. To restart this service, either use Workbench
or see Start or stop the services associated with LiveCycle modules for
instructions.
|
|
|