ASP.NET Performance, 100 "Memory Hard Faults" indiciate a memory swapping problem?
- by Robert
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?