Oracle Point, Oracle Life.

Pool resources consist of two parts: Paged Pool and NonPaged Pool, which are all kernel-mode components created dynamically when a machine boots up. Each of these pools start at an initial size that is based upon the amount of physical memory present in the system. Pool memory is a subset of available memory and is not necessarily contiguous.  If necessary, these pools can grow up to a maximum size that is determined by the system at boot time.

The blog of “Microsoft Enterprise Platforms Support Windows Server Performance team” clearly plots a figure to show some sample maximum values for Paged/NonPaged Pool on x86 system . The post here also introduces a tool “Process Explorer” to diagnose the possible Paged/NonPaged Pool culprits. “Process Explorer” shows you information about which handles and DLLs processes have opened or loaded. This tool can illustrate the details of memory usage and available capacity. once more, it makes it possible to monitor Memory, CPU and I/O usage of individual process . It looks like the following figure, in which I check the resource usage of windows live writer I’m using to compose this post.

The blog of “Microsoft Advanced Windows Debugging and Troubleshooting” offers a feasible way to diagnose “event 2019 and 2020” relating to windows pool usage.

• Find By Handle Count
• By Pooltag (as read by poolmon.exe)
• Using Driver Verifier
• Via Debug (live and postmortem)

You may find couple of helpful Microsoft Windows utilities in this post about tuning and troubleshooting windows memory culprits.

Popularity: 9% [?]