Good morning AskPerf! We’ve had plenty of discussions in the past about Pool Memory – both Paged and NonPaged. Today we’re going to review how we can determine the Pool Memory usage from a memory dump file via the !poolused command. A quick note – if you’re trying to identify a leaking pool tag, analyzing it from a post-mortem dump won’t show you any trends – only the usage as a point in time snapshot. With that, let’s begin as we usually do – looking at the parameters for the command:
|0x1||Displays verbose information|
|0x2||Sort by NonPaged pool memory usage|
|0x4||Sort by Paged Pool memory usage|
|0x8||Display session pool instead of the standard pool (Windows Server 2003 and later)|
If you run the !poolused command with no flags, you will see summary information, sorted by pool tag – as you can see by our first example below. We’re using a dump file today from the same machine that we used to capture data for our post on !vm and !memusage . Remember that you may need to use the GFLAGS utility to enable Pool tagging if it isn’t already enabled.
There’s lots of information here to be sure, but it doesn’t really help up identify the top pool memory consumers – so now let’s try the 0x2 and 0x4 flags. Remember that these are mutually exclusive ...
First our NonPaged Pool used, and now here is our Paged Pool usage:
To refine your results further, you can append the /t parameter to return only the top n rows. As an example, if you ran !poolused /t 10 4 you would get the top ten tags in terms of Paged Pool usage.
For those tags where there is no entry in the pooltag.txt file, you can use the findstr command that we showed you in our post, An Introduction to Pool Tags . OK, there’s one last tip. If you want to filter down the list even further, you can append the TagString parameter to your command as shown below. The second parameter is case-sensitive. Here’s an example of filtering on NonPaged Pool for tags beginning with TCP:
That’s it for this post. A quick post, but this is definitely one of those commands that’s handy to have available! Until next time …
|Share this post :||
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.