Description

In this episode of Defrag Tools, Andrew and I walk you through Sysinternals RAMMap. RAMMap allows you to see how the Physical Memory (RAM) on the computer is being used. You can see how much RAM there is, for what purpose it is being used, and if there has been any memory pressure (not enough memory). We also cover a lot of Memory Management theory to understand the data in RAMMap.

@siodmy: The repurposed of 0-4 is expected. It is the 5-7 that matter. You are getting enough memory pressure on 5 (1.6Gb -- x8 reused) to raise interest at least. Adding a few gigs will definitely help in those times - its not critical though.

Andrew, Please update your Flash player! you should be up to 11.4.402.265you are still using the old 11.3.300.271 which is exploitable. Great Show, I hope you continue to make new shows every week, I look forward to them.

@James G: I use a vhd for the show and it only runs during taping (so I don't add features to the install without you seeing it). The next time I prepare for a show, I'll make sure to give it some time to do the updates. Can't set a bad example can I!

The show will be weekly for at least another ~10 weeks based on the current episode recording schedule. We tape a few at a time if it is the same topic.

Next is vmmap, then we have a special edition, then inbox tools. After that in a yet to be decided order is 3+ on Windows Performance Toolkit, 2+ on Procdump, 4+ on Debugging Tools for Windows, Network Monitor, Fiddler and PsTools. In the maybe bucket is audio, video, printing and device troubleshooting (1 each). We will also probably do a live show on Channel 9 Live at Build.

Lots and lots of shows to watch! If your favorite tool isn't in that list, drop us an email at defragtools@microsoft.com or write a comment and we'll add it to the list or move it forward.

I have a question: you talked about Hyper-V and a vm starts and says to the memory manager hey get me a big part of your ram, and it needs to be continuous. This may work for a fixed memory vm, but what about dynamic memory?

The startup memory block can be 1gb and later need a little bit more, and perhaps find that memory has been occupied by other vm's...

9:40 - 5 GB of RAM in the zero list "which I've never touched since the PC was booted. That RAM is completely wasted." What makes you think it's never been touched? It's not as if RAM, once used, never gets put back on the zero list! It is - as shown by the diagram at 9:51.

btw, it's amusing how closely the diagram at 9:51 resembles the one in VAX/VMS Internals and Data Structures. ;)