Our client ended up filing a ticket to the Microsoft Azure team regarding the issue as this was not expected behaviour.Īnother plus about ProcMon is that you can export the logs to a. What you can't see is that almost all of the 62k events (bottom left figure) are associated with the IIS logging directory.Īfter turning IIS logging off on the server, the tests ran fine and utilisation was back down to normal levels. log file in a folder with the prefix 'W3SVC' - from experience I know this to be IIS logging activity.Īs you can see from the screen shot, there's a lot of read/write/open activity on the log directory. After capturing a few minutes worth of ProcMon data, I immediately saw the problem to be the svchost process writing to a. During our tests we noticed transaction throughput drops and maxed out CPU utilisation on all of the web boxes.
I was working on a project a while back actively performance testing Azure cloud web servers, using JMeter. The best way to demonstrate the power of the utility is to show an example: Example - Web Server IIS Logging ProcMon can help diagnose some major performance problems very quickly and easily by listing (in real time) detailed file, network and registry activity on the screen per a particular process. In Part 1 of the series is a widely used and popular tool called ProcMon (also known as Process Monitor).
In this series of short blog articles, I will discuss some freely available tools you can use to diagnose and resolve performance issues with your applications & servers.
0 kommentar(er)
