Configure offload location | Create a replication domain
Additional disk cache tuning parameters
Overview
In this section we discuss additional disk cache tuning parameters. To configure the custom properties below...
- In the administrative console, click...
Servers | Application servers | server_name | Java and process management | Process definition | Java virtual machine | Custom properties | New- Type the name of custom properties. Include the full property path.
- Type a valid value for the property in the Value field.
- Save the property and restart WebSphere Application Server.
com.ibm.ws.cache.CacheConfig.diskCachePerformanceLevel
Performance level of the disk cache. Valid values are 0, 1, 2, or 3:
Setting to 0 means low performance and low memory usage. A limited amount of metadata is kept in memory.
WebSphere Commerce recommends that you set it to 2 or 3. Default is 1.
For High performance and high memory usage all of the metadata, including dependency IDs and templates, are kept in memory.
Our studies have shown that there is minimal memory overhead using 3. It should definitely be experimented with during load testing. If the heap utilization is acceptable IBM recommends using 3 along with a random eviction policy.
We never recommend 0.
There is no need to perform a disk scan for expiration, for example, no cleanup frequency.
com.ibm.ws.cache.CacheConfig.htodDelayOffloadEntriesLimit xxxx
This property provides a way to limit the buffering of dependency and template information. This limit occurs by specifying an upper bound on the number of cache entries that any specific dependency can contain for buffering in memory. If there are more entries per dependency than this limit, the dependency and template information is written to the disk.
The default is 1000.
WebSphere Commerce recommends that you set it to 100000.
com.ibm.ws.cache.CacheConfig.htodCleanupFrequency
This property specifies the frequency at which the disk cache cleanup daemon removes expired entries from the disk cache.
The default value is zero (0), which means that cleanup is scheduled to run at midnight.
WebSphere Commerce recommends that you set this to 60 (1 hour).
If you have cache entries with small time-out values, you might need to reduce this cleanup frequency.
com.ibm.ws.cache.CacheConfig.htodDelayOffloadxxxx
This property specifies whether extra memory buffers should be used for dependency IDs and templates to delay disk offload and to minimize input and output operations to the disk. This property is enabled by default.
WebSphere Commerce recommends that you explicitly set it to true if you had previously set it to false.
com.ibm.ws.cache.CacheConfig.disableTemplateInvalidation xxxx
This property disables the template-based invalidations during JSP reloads.
WebSphere Commerce recommends that you set it to true.