January 14, 2011 at 5:24 am
SQLkiwi (1/13/2011)
I probably will set Lock Pages in memory after I have finished analyzing what is eating up the remaining 35 GB. But the disadvantage of setting up Lock Page in memory is the start up time will be higher since it enables large Page Extensions if I am not mistaken.
Only if you deliberately enable trace flag 834. See http://blogs.msdn.com/b/psssql/archive/2009/06/05/sql-server-and-large-pages-explained.aspx
Here I will beg to differ from you. You do not need to explicitly set the trace flag 834 to enable large Page Extensions. If your are using Enterprise edition, you have more than 8 GB of RAM and you allow locked pages in memory enabled, large Page Extensions will be set.
I had read the same blog last week when I was investigating our memory issue.. 😀 In that blog it states this as well. I tested it out in our QA box. 🙂 That is why I am able to contradict you on this. 😉 I usually dont get the chance of contradicting you. I got it this time... YAY..!!!!!
-Roy
January 14, 2011 at 6:05 am
Roy Ernest (1/14/2011)
Here I will beg to differ from you. You do not need to explicitly set the trace flag 834 to enable large Page Extensions. If your are using Enterprise edition, you have more than 8 GB of RAM and you allow locked pages in memory enabled, large Page Extensions will be set.I had read the same blog last week when I was investigating our memory issue.. 😀 In that blog it states this as well. I tested it out in our QA box. 🙂 That is why I am able to contradict you on this. 😉 I usually dont get the chance of contradicting you. I got it this time... YAY..!!!!!
Let's be clear. You were concerned that large page extensions would slow start-up time. The behaviour that causes slow start-up is where large pages are used for the whole buffer pool, in which case SQL Server will commit the entire buffer pool at that time, rather than growing it as demand requires. This only occurs when TF834 is set.
Without TF834, the server allocates just 32MB of memory using large pages, and grows the buffer pool according to demand. So, your start-up time will not be slower without TF834, though large page extensions are indeed enabled (but only used by components that specifically request large pages. From the article:
"So LargePageSupport is enabled and used by the engine even if you don’t enable trace flag 834. But not much memory is used for this and buffer pool memory is not used unless trace flag 834 is enabled."
Paul
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
January 14, 2011 at 6:11 am
You are a bad Kiwi... You wont even let me have one small victory? 😀 Thanks for correcting me.. 🙂 That part I did not give much notice.
-Roy
January 14, 2011 at 8:33 am
Roy Ernest (1/14/2011)
You are a bad Kiwi... You wont even let me have one small victory? 😀 Thanks for correcting me.. 🙂 That part I did not give much notice.
I would say he is a very GOOD Kiwi!! 🙂
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 4 posts - 31 through 33 (of 33 total)
You must be logged in to reply to this topic. Login to reply