![microsoft sysinternals suite user guide microsoft sysinternals suite user guide](https://scr.wfcdn.de/10758/Sysinternals-Suite-1409669235-0-0.jpg)
Pages that have been zeroed out and are ready to be used – they can be quickly allocated for new physical memory allocations. Pages that are in transition between any of the other categories. Similar to modified pages but have been marked not to write out to disk. Similar to Standby, but these are pages of physical RAM that have been changed and must be flushed to disk before reusing them. Standby pages are essentially cache – it’s better to have infrequently used data kept in RAM “just in case” than pushing it out to disk when the memory isn’t needed for anything else. These are still left in physical ram but will be repurposed first by the memory manager (either returned to the active list or zeroed out and reused) if something needs physical ram for active pages. Pages of physical ram not actively being used. Pages of physical ram in active use by the specified category (usually a process working set or the system working set). Memory management is a complex beast, so let’s run through a quick refresher of these categories. It allows us to examine detailed memory usage information in a way that is easy accessible.Įach tab has its own wealth of data, but I’ll be focusing on Use Counts and File Summary tab as they offer the information I think most people will be interested in. This tool is called RamMap and it is available from SysInternals at I’d like to talk a bit about a new tool that allows us to examine a vital performance resource: physical memory. My name is Ray Ackley and I’m a Support Escalation Engineer in the Performance specialty. Hello everyone, I’d like to introduce myself. First published on TECHNET on Aug 13, 2010