ASP.NET Performance, 100 "Memory Hard Faults" indiciate a memory swapping problem?

views:

147

answers:

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?

alt text

To see the processor time:

alt text

We will separate the SQL-Server and Webserver very soon.

+2 A:

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?

Jon Skeet 2010-04-11 19:41:06

I added a screenshot that shows the average processor time (50% IIS and 13% Sql-Server). We will separate the sql-sever soon. This will also free some memory resources and should be an interim solution until we get (hopefully) some more traffic. I am still puzzled about "Memory Hard Faults" since I never noticed something like that before.

Robert 2010-04-11 20:10:38

That 50% IIS - is this a dual processor box? If so, that could be a whole processor pegged by one thread.

Jon Skeet 2010-04-11 20:44:01

No the 50% is just coincidence.

Robert 2010-04-12 14:38:25

Indeed the problem is a memory-leak, CPU is only a minor issues, thank you for your insights!

Robert 2010-04-12 14:39:32

ansaurus

tags:

views:

answers:

ASP.NET Performance, 100 "Memory Hard Faults" indiciate a memory swapping problem?

related questions