Expand the Configuration node to select the HTTP Service node.
Click the HTTP File Cache tab.
Define the HTTP File Cache settings as follows:
Globally: Check the Enabled checkbox to enable global file caching.
File Transmission: For Windows only; if checked enables the use of the TransmitFile system call.
Max Age: Enter the maximum age (in seconds) for a valid cache entry. This parameter controls how long cached information is used after a file has been cached. An entry older than the maximum age is replaced by a new entry for the same file. If your content changes infrequently, increase this value for improved performance. Set the maximum age based on whether the content is updated (existing files are modified) on a regular schedule or not. For example, if content is updated four times a day at regular intervals, you could set the maximum age to 21600 seconds (6 hours). Otherwise, consider setting the maximum age to the longest time you are willing to serve the previous version of a content file after the file has been modified.
Max Files: Enter the maximum number of files stored in the file cache. If the value is too big, the server caches little-needed files, which wastes memory. If the value is too small, the benefit of caching is lost. Try different values of this attribute to find the optimal solution for specific applications.
Hash Init Size: Identify the number of hash buckets. The size identified affects memory use and search time.
Medium File Size Limit: Enter a value slightly higher than the VM page size.
Medium File Size: The contents of medium files are cached by mapping the file into virtual memory (Unix/Linux platforms).
Small File Size Limit: Enter a value slightly lower than the VM page size.
Small File Size: The contents of small files are cached by allocating heap space and reading the file into it.
File Caching Enabled: Toggle the caching ON if the file size is less than the Medium File Size Limit.
Click Save to save the changes, or Load Defaults to return to the default settings.