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

MemToLeave (Non-Buffer Pool) Expand / Collapse
Author
Message
Posted Tuesday, January 29, 2008 2:54 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, May 1, 2014 1:31 AM
Points: 42, Visits: 300
Does anybody know a good way to identify what is fragmenting my MemToLeave area?

I am using LiteSpeed SQL 2005 on an SQL Server 2005 Enterprise SP2 default installation running on Windows 2003 Enterprise SP2. Total RAM is 16 GB. I am using AWE, PAE, and 3GB. The min and max server memory are fixed at 14595 MB. The startup parameter -g is 512.


I just discovered an extended stored procedure (xp_memory_size) that LiteSpeed installs to show the largest contiguous block of MemToLeave is very low 4 mb.

Litespeed backup and restore is taking long time. we upgraded sql server 2000 to sql server 2005 inplace. before upgrade we removed lite speed and installed after upgrade. before upgrade there is no issue.



All ideas and suggestions will be appreciated.

Thanks.



Post #449103
Posted Tuesday, January 29, 2008 11:28 PM


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 @ 12:15 PM
Points: 43,017, Visits: 36,179
Do you have any linked servers in use? Using CLR?


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 #449184
Posted Wednesday, January 30, 2008 3:27 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, May 1, 2014 1:31 AM
Points: 42, Visits: 300
There is 2 linked servers and no clr.



Post #449722
Posted Wednesday, January 30, 2008 11:15 PM


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 @ 12:15 PM
Points: 43,017, Visits: 36,179
Linked server drivers use the MemToLeave area. I've had a case of a buggly driver leaking memory in MemToLeave and causing slow backups and eventually a system crash.

The thread stacks are also in the MemtoLeave area.

Are you running x86, x64 or IA64 architecture? What drivers do those two linked servers use?



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 #449817
Posted Thursday, January 31, 2008 10:44 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, May 1, 2014 1:31 AM
Points: 42, Visits: 300
Thanks for reply. We are using X86 and linked server we are using sql native client provider. we did inplace upgrade from sql server 2000 to sql server 2005. Automatically updated providers also.



Post #450087
Posted Thursday, January 31, 2008 10:55 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 @ 12:15 PM
Points: 43,017, Visits: 36,179
Than I'm stumped. Sorry. Maybe someone else here has an idea. If you're got a support contract with MS, consider logging a case with PSS.

I've had very bad experiences with drivers for the AS400 on an IA64 box, but SNAC in x86 should be fairly well behaved.

What you could try is logging the results of xp_memory_size at regular intervals after a server restart. If you can find out when the memory gets fragmented, maybe you can figure out what's causing it.

Maybe unrelated, but if your max and min memory settings are the same, maybe reduce the min by a couple MB. I've heard (but it may just be urban legend) that setting max and min memory to the same value stops a couple of memory management routines from running.



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 #450092
Posted Thursday, January 31, 2008 3:11 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, September 15, 2014 7:22 AM
Points: 1,523, Visits: 2,200
I've had that issue with Idera SqlSafe before...their extended stored procedures fragmented it. I'm sure they have improved since I used it, but at the time the only solution they were able to give me was to bounce the service occasionally. Perhaps LiteSpeed is similar?

Jason Shadonix
MCTS, SQL 2005
Post #450213
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse