Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Memory Leak SQL 2008 R2 64 bit? Expand / Collapse
Author
Message
Posted Tuesday, September 11, 2012 12:33 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 5:56 AM
Points: 1,068, Visits: 3,033
TotalServerMemoryMB - 3270.125000


For the Lock page memory enable
---------------------------------
Lock Pages in Memory is a setting that can be set on 64-bit operating systems that essentially tell Windows not to swap out SQL Server memory to disk. By default, this setting is turned off on 64-bit systems,

Yes, that is correct, lpim is off by default but you have it turned on and you still have not told us why you enabled it.



for this reason enable LPIM in x64 operating system.

SQL service accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk. also memory may boost performance when paging memory to disk is expected.






Post #1357156
Posted Tuesday, September 11, 2012 1:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 10:47 AM
Points: 7,126, Visits: 12,727
ananda.murugesan (9/11/2012)
TotalServerMemoryMB - 3270.125000

Thank you. This confirms what was mentioned before. At present there are no indicators that anything out of the ordinary is occurring in terms of how much memory SQL Server is using on your server.

For the Lock page memory enable
---------------------------------
Lock Pages in Memory is a setting that can be set on 64-bit operating systems that essentially tell Windows not to swap out SQL Server memory to disk. By default, this setting is turned off on 64-bit systems,

Yes, that is correct, lpim is off by default but you have it turned on and you still have not told us why you enabled it.



for this reason enable LPIM in x64 operating system.

SQL service accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk. also memory may boost performance when paging memory to disk is expected.

There is a great debate about this in the SQL Serevr community. Some prefer to enable lpim on x64 Windows Server 2008 R2 running SQL Server 2008 R2 by default, and others prefer (including myself) to leave lpim disabled unless the database server exhibits specific behavior that signals there may be a benefit to enabling lpim.

Here is a good primer on the debate and one of many articles and my own experience that helped shape my opinion: Great SQL Server Debates: Lock Pages in Memory (12 December 2011) by Jonathan Kehayias

When SQL Server approaches 7.5 GB do you start to see system instability or messages entering the SQL Server Error Log signifying the server is under memory pressure? If not then you should be happy with your server configuration. If so, please post those messages here.


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1357168
Posted Tuesday, September 11, 2012 1:51 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 5:56 AM
Points: 1,068, Visits: 3,033

Thanks for reply

I do have a question though.

Server OS’s are x64, and even though I have set the value for LPIM with the service account, I have never seen a message in the SQL log stating “Using locked pages for buffer pool” on any of the servers. Did I miss something?


I have noticed before enable LPIM in this box, In Task manger showing sqlservr.exe consuming 6.4 GB constantly and exceeds max memory setting. periviously I have setting max memory 5 GB, but sql server is not using max level. after that I have enabled LPIM and setting max memory 6114 MB.

Performance Tap in task manager why 7.5 GB consuming physical memory using after restarted SQL services, it was totaly reduced and now comsuming 4.55 GB only...thats what I have mention first post memory leak sql 2k8 r2.

OS level (Win 2008 R2 64 bit)there is no service pack installed, It is RTM. Does SP is require to be installed on OS side?

thanks





Post #1357179
Posted Tuesday, September 11, 2012 2:48 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 8:19 AM
Points: 40,208, Visits: 36,617
ananda.murugesan (9/11/2012)

Performance Tap in task manager why 7.5 GB consuming physical memory using after restarted SQL services, it was totaly reduced and now comsuming 4.55 GB only...thats what I have mention first post memory leak sql 2k8 r2.


There is no memory leak.

SQL uses as much memory as it needs up to max server memory + a bit for the non-buffer memory. All that the 4.5 GB now tells us is that SQL has only needed 4.5 GB of memory since the restart. Everything you've shown so far shows a SQL Server that's working fine and as expected.

Again, don't use Task Manager to show SQL's memory usage, it shows incorrectly (fault of Task Manager, not SQL Server) if locked pages is enabled.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1357201
Posted Tuesday, September 11, 2012 3:19 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, October 21, 2014 5:56 AM
Points: 1,068, Visits: 3,033

Thanks

one final clarifications, still I am not getting conclusion about LPIM setting.

1.SQL SERVER 2008 on top of Windows 2008 enterprise edition both x86 and x64

2.SQL SERVER 2008 R2 on top of Windows 2008 R2 enterprise edition both x86 and x64

Which & when condition needs to be enable LPIM for both environments?
Post #1357225
Posted Tuesday, September 11, 2012 3:42 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 8:19 AM
Points: 40,208, Visits: 36,617
Did you read the article that Opc linked?

opc.three (9/11/2012)
Here is a good primer on the debate and one of many articles and my own experience that helped shape my opinion: Great SQL Server Debates: Lock Pages in Memory (12 December 2011) by Jonathan Kehayias



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1357241
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse