Lock Pages in Memory ... do you really need it?

re: Lock Pages in Memory ... do you really need it?

jerry lagrou — Tue, 29 Apr 2008 20:45:30 GMT

Help.

I have 32GB Installed.

I have 64-bit OS. (Windows Server 2003R2)

I have 64-bit SQL Server 2005 9.0.3042

I have minimum server memory 2048

I have maximum server memory 28669

My sql server will only use 650MB of memory.

I have no idea why.

help!

jerry@lagrou.org

re: Lock Pages in Memory ... do you really need it?

colin leversuch-roberts — Thu, 01 May 2008 11:38:43 GMT

Another excellent post, thank you. I do wish you guys would get together with the SQL guys though as I figure most DBA's probably won't view your blog, I shall promote your blog again of course.

re: Lock Pages in Memory ... do you really need it?

stephc — Fri, 01 Aug 2008 21:17:04 GMT

(Answer to jerry lagro)

The 650MB you see sql server using is presumably from its private bytes.

The larger dedicated /lock pages in memory usage is not reflected in the private bytes counter

(nor in the working set counter)

re: Lock Pages in Memory ... do you really need it?

Johan Bijnens (ALZDBA) — Fri, 05 Sep 2008 10:53:16 GMT

Is there any way sysinternals "Process Explorer" can help out in figuring out memory consumption on this issue ? (or another sysinternals tool)

re: Lock Pages in Memory ... do you really need it?

MrMMills — Mon, 17 Nov 2008 23:05:35 GMT

Run Process Explorer the current one will work for x86 and x64.

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Go to View, Select Columns, then choose the Process memory tab. Now select Page Faults, Private Bytes, Virtual Size.

You may also want to go back and choose the .Net tab and select "Contentions" (located at the bottom)

This tool has really "enlightened" me on the fact that my SQL environments really need to be tuned better.

re: Lock Pages in Memory ... do you really need it?

mrmmills — Mon, 17 Nov 2008 23:06:19 GMT

Run Process Explorer the current one will work for x86 and x64.

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Go to View, Select Columns, then choose the Process memory tab. Now select Page Faults, Private Bytes, Virtual Size.

You may also want to go back and choose the .Net tab and select "Contentions" (located at the bottom)

This tool has really "enlightened" me on the fact that my SQL environments really need to be tuned better.

re: Lock Pages in Memory ... do you really need it?

monkston — Fri, 22 May 2009 18:02:37 GMT

We have a 32-bit system, where for a variety of reasons we are removing AWE but are enable to disable lock pages in memory as remove appears to be greyed-out in the Group Policy.

Any ideas?

Thanks

re: Lock Pages in Memory ... do you really need it?

monkston — Fri, 22 May 2009 18:03:13 GMT

Sorry I meant unable to disable