Memory Management - Understanding Pool Resources

re: Memory Management - Understanding Pool Resources

Billy Dhillon — Wed, 11 Apr 2007 19:38:37 GMT

So has the Product Team considered putting in the actual Pool Tag in the Event ID thats leaking since GFLAGS is enabled by default on 2K3+?

End of 32-bit Windows Servers

꼬알라의 하얀집... — Sat, 21 Jul 2007 12:34:25 GMT

언제까지 32-bit 서버 운영 체제가 출시되나요? 라는 질문을 가끔 받습니다. 주말에 이런저런 생각을 정리하다 보니, 2004년에 제가 발표했던 x64 관련 슬라이드가 보였습니다.

re: Memory Management - Understanding Pool Resources

Martin Necas — Fri, 14 Sep 2007 16:40:11 GMT

Are there any chance to determine, which process(es) is using (and how much) memory allocation through "MmAllocateContiguousMemory".

I have an high consumption of nonpaged memory pool and only thing i see in PoolMon is MmCm flag with 40 MB in size.

I am running almost out of nonpaged memory, because I am running with /3GB (Exchange).

Thanks

Troubleshooting Server Hangs - Part One

Ask the Performance Team — Tue, 25 Sep 2007 17:04:25 GMT

Following on from our post on troubleshooting a basic application crash , it's time to start troubleshooting

Memory Management - x86 Virtual Address Space

Ask the Performance Team — Fri, 28 Sep 2007 17:35:32 GMT

In previous posts, we've discussed the Basics of Memory Management , Pool Resources and of course the

re: Memory Management - Understanding Pool Resources

Spooky — Mon, 15 Oct 2007 03:37:06 GMT

Hello there,

I have to ask, what exactly is the issue with the Terminal Services? They are installed by default on Windows XP and it seems that I can't increase the paged pool memory size, it's always bound to 160 mB. Does anybody have more details on this?

Troubleshooting Event ID 333 Errors

Ask the Performance Team — Tue, 30 Oct 2007 16:14:16 GMT

In previous posts we've discussed the basics of memory management including an overview of kernel and

re: Memory Management - Understanding Pool Resources

Bill — Tue, 06 Nov 2007 21:27:40 GMT

will more ram give you more paged pool memory?

re: Memory Management - Understanding Pool Resources

Loren Eslinger — Mon, 12 Nov 2007 18:59:01 GMT

Nice feature adding in the NonPagedPool and PagePool limits to this tool. This is a littler nicer interface than having to use LiveKD to get the same maximum/limits for these values.

Troubleshooting performance issues and understanding memory go hand and hand.

Looking forward to the "Coming soon - Memory Tuning, Troubleshooting Memory Issues and Using the /3GB switch" Some indepth discussion on using /3B and /PAE with Exchange would be interestings. How do get around the NonPagedPool and Free System pages being cut in 1/2 when using /3GB switch?

re: Memory Management - Understanding Pool Resources

Megan — Tue, 13 Nov 2007 00:08:39 GMT

Thanks for the great article! For clarification the article states "the Memory Manager creates two dynamically sized memory pools that kernel-mode components use to allocate system memory". Can you be more specific? Are these tables by which the kernel can place pointers in?

re: Memory Management - Understanding Pool Resources

pau — Mon, 17 Dec 2007 12:31:50 GMT

hi, how can i get kernel memory for a specific process?

"Page cannot be displayed" due to Non-Paged Pooled Memory Depletion

kybernetegisms — Thu, 21 Feb 2008 04:07:05 GMT

Overview It’s not unnatural to assume an IIS process hang when web client browsers begin reporting either

"Page cannot be displayed" due to Non-Paged Pooled Memory Depletion

Noticias externas — Thu, 21 Feb 2008 04:51:14 GMT

Overview It’s not unnatural to assume an IIS process hang when web client browsers begin reporting either

re: Memory Management - Understanding Pool Resources

ranjan — Fri, 16 Jan 2009 07:35:25 GMT

found it very useful. thanx.

Ranjan

blog.ranjangaur.com

re: Memory Management - Understanding Pool Resources

San — Sat, 21 Mar 2009 01:10:46 GMT

If i say exchange runs in Page pool memory is that a correct statement?

re: Memory Management - Understanding Pool Resources

Harish — Mon, 10 Aug 2009 09:49:04 GMT

What about the PagedPoolSize limits for WinXP by default in 1GB Ram and in 512MB ram.

"On both Windows 2000 and Windows 2003, the HKLM\System\CurrentControlSet\Control\Session Management\Memory Management\PagedPoolSize value can be set to 0xFFFFFFFF"

Is this applicable to Windows XP the same way it applies to Windows 2000 ?