Nearly 200 MB nonpaged pool used in VM after fresh start

Question

I noticed  that a newly installed 2012R2  ( smallest instance for that example)  has over 200MB  nonpaged pool in use.
logman query -ets
WindowsAzure-GuestAgent-Metrics         Trace                         Running
WindowsAzure-GuestAgent-Status          Trace                         Running
WindowsAzure-GuestAgent-Diagnostic      Trace                         Running
stopping These 3 guys
logman stop WindowsAzure-GuestAgent-Metrics -ets
logman stop WindowsAzure-GuestAgent-status -ets
logman stop WindowsAzure-GuestAgent-diagnostic -ets
and NPP usage  Drops from 217MB  to ~25MB
as much as I'm into diagnostic traces  -  this eats up ~25%  of the available  Memory in a 768 MB  VM  instance.
this is clearly  too much.
can These Loggers  :
turned off permanently ?
tweked to  reduce  buffersize  and/or numbuffers   permanently?
thanks,
Christian

Answer 1

Hi,
The memory manager in 32-bit Windows Vista and later, including Server 2008, Server 2012 and Windows 7 (there is no 32-bit version of Windows Server 2008 R2) doesn’t carve up the system address statically; instead, it dynamically assigns ranges to different
types of memory according to changing demands. However, it still sets a maximum for nonpaged pool that’s based on the amount of physical memory, either slightly more than 75% of physical memory or 2GB, whichever is smaller. 
Here’s a table summarizing the nonpaged pool limits across different version of Windows:
32-bit
64-bit
XP, Server 2003
up to 1.2GB RAM: 32-256 MB  
> 1.2GB RAM: 256MB
min( ~400K/MB of RAM, 128GB)
Vista, Server 2008, 
Windows 7, Server 2008 R2
min( ~75% of RAM, 2GB)
min(~75% of RAM, 128GB)
Windows 8, Server 2012
min( ~75% of RAM, 2GB)
min( 2x RAM, 128GB)
Hope this helps !
Regards,
Sowmya