Super User is a question and answer site for computer enthusiasts and power users. 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

Windows 7 resmon displays 0 hard faults. But perfmon shows pagefault around 60 and perfmon /report tells me my system swaps actively.

AFAIK not every page fault is hard fault: page could be stored in cache, that is "standby" memory, right?

So I really do not have memory bottleneck but perfmon simply does not know about Windows 7 memory management (where pagefault != hardfault)? If so how can I trace swap usage on my PC? (there is no "hardfault" counter in perfmon)?

I found that I should use "Pages Input" and "Pages Output" to get number of pages read / written to disk and "Page Read" / "Page Write" to get number of read / write requests.

But I still can't get why "permon / report" tells me I need to install more memory if "Pages Input / Output" is about zero..

share|improve this question

migrated from May 6 '12 at 0:55

This question came from our site for system and network administrators.

It is telling you that you need to install more memory because the cache hit rate is low, suggesting that the system working set exceeds physical memory. Paging will only happen if the system is unable to shrink the cache, but performance will suffer even if it is. – David Schwartz May 5 '12 at 20:55
@David: I'm not sure how you get to that conclusion from soft faults. The situation you describe would cause hard faulting. – Ben Voigt May 6 '12 at 1:16
@BenVoigt: Not if the problem is that the cache is too small, not that mapped pages aren't resident. Consider, for example, a web server. The number of mapped pages is very small, but the need for disk cache is very great. If physical memory can't hold the set of frequently accessed small files, performance will suffer but not due to page faults. – David Schwartz May 6 '12 at 18:52
@David: If the web server using memory mapping to read the files, you'll have page faults. Otherwise, you'll have normal disk I/O. Neither one would cause soft faults, AFAIK. – Ben Voigt May 6 '12 at 21:54
@BenVoigt: I can't tell if you're disagreeing with me or not. It sounds like we agree. He could have normal disk I/O caused by insufficient physical memory leading to poor performance. The absence of hard page faults doesn't mean that insufficient physical memory isn't an issue. (I'm not trying to explain the soft page faults, I'm trying to explain his issue.) – David Schwartz May 6 '12 at 22:04

Soft faults occur when the page table entry is not in the page table, but the page is in RAM. I think the TLB size is fixed for a particular processor, so there isn't much an end-user can do about soft faults. (A programmer can optimize his code for better locality, which reduces the number of TLB misses and soft faults.)

share|improve this answer
I'm not sure what this has to do with his problem. His problem is poor performance and high disk I/O. This might make a good comment, but it's not an answer. (Unless you think the soft faults have something to do with his actual problem. Which you don't say and don't provide any evidence for.) – David Schwartz May 6 '12 at 22:06
@David: I understand the question differently. He's reporting a number of soft page faults, and asking whether that means he has a performance problem. – Ben Voigt May 6 '12 at 22:09
Then the answer would be a simple "no". (At least, not unless it's an absurdly high number.) But as I understand the question, he wants to know why he's being told he needs to install more physical memory. – David Schwartz May 6 '12 at 22:50

You must log in to answer this question.