ASP.NET Performance, 100 "Memory Hard Faults" indiciate a memory swapping problem?
With a customer web site we currently experiences performance problems.
While analyzing the problem we found an unexpected amount of of 112 "Memory Hard Faults" per minute. Does anybody can interpret the meaning of this value? Does this happen, when memory swapping is necessary - so the root cause is not sufficient memory?
Even if the CPU value seems high, it is not the main problem for the slow web site. Do you agree?
To see the processor time:
We will separate the SQL-Server and Webserver very soon.
You've got a working set of nearly 4GB for w3wp.exe. Yes, this sounds like you've got a memory problem.
That doesn't necessarily mean that you just haven't got enough memory though - my guess is that you've got a leak somewhere. That amount of CPU usage is disturbingly high too. How much of the processor is being used by the web site?
Also, it looks like the database and the web site are being run on the same host - are you able to separate them?