Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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

What does this option basically do? Does it free the unused memory? If so, how does it affect the performance? In what cases will I use it?

share|improve this question
up vote 1 down vote accepted

Excerpt from my copy of Windows Sysinternals Administrator's Reference 1st ed:

Empty Working Sets Removes memory from all user-mode and system working sets to the Standby or Modified page lists. Note that by the time you refresh RAMMap’s data, processes that run any code will necessarily populate their working sets to do so.

Empty System Working Set Removes memory from the system cache working set.

From personal experience, I just used taskmgr to view the memory changes.

Initial - 6.41 GB

After opening RamMap - 7.19 GB

After doing Empty working set - 5.45 GB

Close RamMap - 4.68 GB

Also, an image of the same below: -

enter image description here

share|improve this answer

From the VMMap Help manual:

The Empty Working Set menu item in the Refresh menu releases all physical memory assigned to the process and then refreshes the scan.

I would assume that the feature is similar for RAM map and that the "Empty Working Set" feature releases all physical memory.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.