Sorry for the strange quoting, that was me using nabble.com ... My reply should also contain (but does not - don't know what went wrong):
I've installed LambdaProbe and it tells me that there are not much Threads (about 50) and most of them are in state of waiting or timed_waiting. So that seems to be okay - but what if Tomcat sent the response to the first user request and then does the logging, while the next request or other users are waiting? And this: The log files are under 20 MB, that should be fine, shoundn't it? The disk is way far from beeing full and it's a RAID1 with SCSI disks so they should have enough performance. I'm now totally unsure if I should enable access.log-files (to have statistics with AWstats) or disable them (to have more performance) ... Frank Frank Niedermann wrote: > > Tim, > > > Tim Funk wrote: >> >> 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. > The log files are under 20 MB, that should be fine, shoundn't it? The disk is way far from beeing full and it's a RAID1 with SCSI disks so they should have enough performance. I'm now totally unsure if I should enable access.log-files (to have statistics with AWstats) or disable them (to have more performance) ... Frank -- View this message in context: http://www.nabble.com/Performance-decreasing-if-access.log-enabled-tf2408485.html#a6715985 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
