Monitoring memory usage in Windows helps explain sluggish performance, sudden application slowdowns, and system-wide stalls that often appear when physical RAM is under sustained pressure.
Performance Monitor (perfmon) reads metrics from the Windows performance counter subsystem and charts them in real time or logs them for later review. Memory-focused counters such as Available MBytes, Committed Bytes, and Pages/sec provide a clearer picture of memory pressure than a single “in use” number, especially when paging and commit behavior matter.
Short spikes are normal during startup, app launches, updates, and resume-from-sleep events, so sustained trends matter more than one-off peaks. Long-running logging sessions can grow quickly, and creating Data Collector Sets may require elevated permissions depending on policy and log location.
Use Ctrl + Shift + Enter to start perfmon elevated when access is denied.
The Select counters from computer field targets a remote system when permissions and firewall rules allow.
Available MBytes trends toward zero under pressure, Committed Bytes trends toward the commit limit as virtual memory demand grows, and Pages/sec reflects paging activity (short bursts can be normal).
Select an unwanted default counter in the legend and press Delete to remove it from the view.
The set name also appears under User Defined and Reports.
Shorter intervals increase detail and increase log size.
The default root directory is often C:\PerfLogs\Admin.
Leaving a data collector set running indefinitely can consume significant disk space and reduce the usefulness of the capture.