The AccessLog writing only occurs *after* the response has been sent to the client and the request is essentially done. I think if there is a performance issue - it is OS/filesystem specific. We pounded some HPUX boxes with and without access logs turned on. As long as we did not run out of processors, we didn't see any performance differences.
It might be of interest to parse and decode the pattern at set time for AccessLogValve (like the ExtendedVersion does) to prevent a lot of extra string comparisons. (If the user chooses a custom pattern) But I'm indifferent because of the results I posted above.
On a stressed system, this might still be a good thing todo.
-Tim
Remy Maucherat wrote:
Remy Maucherat wrote:
Adding new items:
- Use this to try to provide an optimized version of the access logging valve (access logging is likely used in production for standalone Tomcat, and it has very bad performance right now) which would do asynchronous writes to its file (and hopefully be more efficient)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
