Setting the Caching Proxy directive MaxLogFileSize too low affects performance
 Technote (troubleshooting)
 
Problem(Abstract)

The Caching Proxy directive MaxLogFileSize does not reflect the actual size of the log file when the value of the directive is set too low. Setting the value too low also affects performance of the proxy.
 
Cause
Due to performance reasons, the proxy server buffers logging entries and flushes the buffer to disk when the buffer is full. When the value of MaxLogFileSize is set too low, for example, less than 1 M, the actual log file size might be much greater than the value due to the use of buffers.
 
Resolving the problem
The recommended value for setting the MaxLogFileSize directive is at least 10 M, but less than 200 M. The actual log file size is slightly larger than the size that you set. Setting the value too low affects the proxy performance because the proxy server closes and opens the log file more frequently.
On some platforms, setting the value too high causes the proxy to use more memory for I/O buffering. When the log file size becomes larger, it can cause the proxy to run out of memory or look like a memory leak, even though the I/O buffers are controlled by the operating system.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Edge Server Caching Proxy Multi-Platform Edge Server 2.0 GA
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1207394
IBM Group: Software Group
Modified date: Sep 3, 2007