Exercise 2: 90% Memory Usage on a Responsive Machine — Possible Solution ==================================================================== WHY HIGH MEMORY USAGE ALONE ISN'T PROOF OF A PROBLEM ------------------------------ Per this chapter, "high memory usage alone doesn't necessarily mean a machine is struggling - Windows deliberately caches aggressively, and 'available' memory being low is often just unused cache ready to be reclaimed instantly." Windows intentionally fills otherwise-idle memory with cached data (recently used files, application data) specifically because unused RAM provides no benefit sitting empty - that cached data can be instantly discarded the moment something else actually needs the memory, with no performance penalty at all. WHY THIS EXPLAINS THE MACHINE FEELING RESPONSIVE ------------------------------ If most of that 90% usage is Windows's own deliberate caching rather than genuine memory pressure, there's no actual shortage forcing the system to struggle - the cached data is simply occupying otherwise-idle space, ready to be freed instantly if needed, which is exactly why the machine can feel perfectly responsive despite the high percentage shown. THE MORE RELIABLE INDICATOR ------------------------------ Per this chapter, "the more reliable indicator of real memory pressure is Hard Faults/sec, visible in Resource Monitor's Memory tab: a hard fault means data had to be read back from disk because it had been paged out, a genuinely expensive operation and a much more direct sign of insufficient memory than the raw usage percentage alone." Checking Hard Faults/sec rather than the overall percentage would show whether the system is actually being forced to swap real, needed data back and forth to disk (true memory pressure) versus simply having a lot of reclaimable cache in use (no real problem at all). WHY THIS DISTINCTION MATTERS PRACTICALLY ------------------------------ A support engineer troubleshooting sluggishness based on the memory percentage alone risks chasing a non-issue, or recommending a RAM upgrade that wouldn't actually help, when the real signal - a low or near-zero Hard Faults/sec figure - would have shown the high percentage was just healthy caching all along. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains why Windows's own deliberate caching behavior makes high memory usage alone unreliable as a distress signal, connects that directly to why the machine can still feel responsive, and names Hard Faults/sec as the specific, more reliable metric this chapter recommends checking instead.