1-6 Administrators Guide for Dynamic Converter
change that occurred for the corresponding source content item. The updated time stamp, as a result, will be recognized by Dynamic Converter, and the content item,
with metadata updates, will be reconverted.
Database Method of Checking You can choose to use the database method of checking whether the content items
metadata has been updated. You set this option on the Dynamic Converter Configuration page see
Conversion and Caching Optimizations on page A-7. With
this configuration option enabled, content item updates continue to signal timestamp changes in the converted files, but the new caching and querying method is not used
to determine if the content items are up to date. Instead, the Content Server database is queried for this information. You might use this method, for example, if you are
experiencing problems with the optimized query Element or you are troubleshooting a related issue.
1.8.3 Timestamp Checking Frequency
By default, Dynamic Converter checks the time stamp of the converted content items every 1,500 milliseconds, or 1.5 seconds. You can increase or decrease this value if you
would like to balance the number of queries performed with the number of visitors to your site. You can change the timestamp checking frequency on the Dynamic
Converter Configuration page see
Conversion and Caching Optimizations on
page A-7. If you increase this setting to, say, one minute 60,000 milliseconds and a new content
item is checked into the Content Server, then the new version will not be available to users until one minute has passed.
1.8.4 Cache Interval
The cache interval is the frequency with which the conversion cache is evaluated and cached items may be considered for deletion, depending on how long they have been
in the cache and their conversion status. You can set the cache interval in days on the Dynamic Converter Configuration page see
Conversion and Caching Optimizations on page A-7. The default is seven days i.e., once every week.
1.8.5 Cache Size
Dynamically converted files are kept in a cache to avoid unnecessary re-conversion. You can set the maximum cache size on the Dynamic Converter Configuration page
see Conversion and Caching Optimizations
on page A-7. The default is 10,000 MB about 10 GB. If the cache exceeds this maximum size, then during the next clean-up
cycle which, by default, is seven days the cached items that have not been accessed for the longest period of time are deleted first. The list for deleting is sorted by the
last accessed date in ascending order. If the cache size limit is not exceeded, then the cached items are examined for potential deletion in the same order, but items that are
forced conversions of existing documents are not deleted.
1.8.6 Cache Expiration Period
Dynamic Converter keeps converted content items in the Web Layout conversion cache to prevent items from being reconverted unnecessarily. You can control the
number of days that must pass before converted items in the cache may be considered for deletion. By default, cache clean-up is evaluated every seven days. Date expiration
only applies to cached items for documents that are no longer present and to cached
Introduction 1-7
items that were not generated by forced conversion see Forced Conversions
on page 1-4. The default cache expiration period is seven days.
The cache expiration setting works in conjunction with the cache interval see Cache
Interval on page 1-6, which controls the frequency with which the cache is evaluated.
For example, if the cache interval is set to 14 days and the cache expiration period is set to 8 days, then the cache will be evaluated every 14 days and all cached items older
than 8 days will be deleted unless they were the result of forced conversion.
1.9 Special Conversions
