| Measurement |
Description |
Measurement
Unit |
Interpretation |
| No_of_Cache_Hits |
Indicates the number of cache lookup hits during last measurement period.
|
Number |
|
| No_of_Cache_Misses |
Indicates the number of cache lookup misses during last measurement period. |
Number |
|
| No_of_Cache_Content_Hits |
Indicates the number of hits on cached file content during last measurement period. |
Percent |
|
| Cache_Content_Misses |
Indicates the number of misses on cached file content during last measurement period. |
boolean |
|
| No_of_File_Info_Lookups |
Indicates the number of hits on cached file information during last measurement period. |
Number |
|
| No_of_FI_Lookup_Failures |
Indicates the number of misses on cached file information during last measurement period. |
Number |
|
| No_of_Entries |
Indicates the number of current cache entries. |
Number |
|
| Maximum_Cache_Size |
Indicates the maximum number of cache entries. |
Number |
The optimal file cache size is dependent on whether you are running a 32-bit or a 64-bit server. The available address space for a 32-bit server is limited to 4GB. The max-entries for file cache is based on the amount of Java heap, the number of threads (as specified by thread-pool/max-threads), and the connection queue size. It is recommended to cache small, frequently accessed static files in the file cache and use perfdump to ensure that the file cache hit ratio is close to 100%. To achieve this, you may increase file cache size and fine tune the max-entries for optimal performance. In a 64-bit server, due to the increased availability of address space, you can cache more static content in the file cache.
|
| No_of_Open_File_Entries |
Indicates the number of current open file entries. |
Number |
|
| Max_Open_Files_Allowed |
Indicates the maximum number of open files allowed. |
Number |
|
| Heap_Size |
Indicates the current heap size. |
MB |
|
| Maximum_Heap_Cache_Size |
Indicates the maximum heap cache size. |
MB |
The optimal cache heap size depends upon how much system memory is free. A larger heap size means that the Web Server can cache more content and therefore obtain a better hit ratio. However, the heap size should not be so large that the operating system starts paging cached files.
|
| Size_of_Mem_Mapped_File |
Indicates the size of memory mapped file content. |
KB |
|
| Max_Mem_Mapped_File_Size |
Indicates the maximum size of memory mapped file. |
KB |
|
| Maximum_Age_of_Entries |
Indicates the maximum age of a valid cache entry. |
Secs |
The 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.
|
| File_Cache_Enabled |
Indicates the file cache is enabled or disabled. |
Boolean |
|