Unless you are max'd on working threads - access logging should not be a
performance hit. Access logging takes pace after the response is sent to
the client.
BUT if the access logs are big, AND you a re low on disk, AND/OR your
disk is SLOOOOW then that could be a problem. The overhead of logging
the access log is pretty low.
-Tim
Frank Niedermann wrote:
Hi,
my users are experiencing increasing performance if I enable access.log:
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative
to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a
relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="access." suffix=".log"
pattern="combined" resolveHosts="false"/>
Is that possible or do I have another performance issue?
Is there a way to see what Tomcat is doing right now? Maybe the logging is
using too much JVM ressources and therefore steals performance from Tomcat -
but I don't know how to evaluate this.
Regards,
Frank
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
