Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a major issue with our load balance web servers. If we have IIS logging turned on for our biggest websites, it bogs the servers down so much that most of our requests timeout. As soon as I turn the logging off, the server run fine again. What are some plausible solutions to being able to have logging for our web traffic and not have this bottleneck?

We have 2 load balance VMWare virtual servers running Windows Server 2003 and IIS 6 that handle just our websites/web traffic and nothing else (database and mail are on different servers).

EDIT: One wrinkle I forgot is that the files are saving to separate file server which is attached to a NAS.

share|improve this question
up vote 1 down vote accepted

Is the server logging to the same disk as the sites are being served from? You might check to see what your average disk I/O times are looking like with logging enabled. Shifting the writes to another drive may help speed things up.

share|improve this answer
Oh!!! One wrinkle I forgot is that the files are saving to separate file server which is attached to a SAN. – Jeremy Sullivan Jun 16 '09 at 0:18
The latency over the network to the SAN is likely your bottleneck. Can you try logging to a local disk for a short period to see if that improves performance? – Justin Scott Jun 16 '09 at 0:55
Yes, moving the files to the local disk resolved the latency, but now, I have two different log files. shrug I'm a developer, not a hardware guy. :) – Jeremy Sullivan Jun 17 '09 at 1:29

If all you care about are the actual pages (HTML, ASPX, etc.) that are being accessed, then perhaps move your other static resources (images, css, js) to separate folders -- if they aren't already segregated -- and then disable logging for those folders. Since each web page usually loads multiple other static resources, you may be able to reduce your logging activity considerably while still logging access to the pages you care about.

share|improve this answer
It would have been more helpful if you explained how to reduce logging to only the pages you care about... – Dscoduc Jun 16 '09 at 18:00

You could consider limiting what is being logged in IIS. For example, suppose you don't need to log the access to every image file, script file, or whatever. There is an option in IIS 6 to limit what gets logged:

Limit what gets logged in IIS

and doing the same in IIS 7 is a little different:

Limit what gets logged in IIS 7

I implemented this on my web server, removing images, scripts, and some misc handlers and noticed the log size was about 75% smaller than before. Obviously when doing this you are unable to see entries in the log files for excluded items, but I was mainly concerned with page access.

share|improve this answer

I've read in the comments that you are logging to a SAN. To confirm if the SAN's latency characteristics are causing the issues, try logging to the hard drive for a day.

share|improve this answer

You should carefully examine your storage, probably its write performance is inadequate. You can also check what RAID level is being used. If it is RAID 5, you should consider going to a faster array like RAID 10, 01, 10E. You might also consider creating a separate RAID volume just for the logs, so that it does not interfere with IIS operation.

Besides, your are probably confusing NAS and SAN. Those are different technologies performance wise. If you are indeed using NAS, you should think twice, as this technology is not always suited for high I/O load.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.