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

Failure to calculate super-latch promotion threshold Expand / Collapse
Author
Message
Posted Friday, December 28, 2012 8:29 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, December 14, 2014 12:07 PM
Points: 342, Visits: 834
I just checked all the servers that we've received the error from and here are the version numbers...

SQL 2012 - 11.0.3000
SQL 2008 R2 - 10.50.4000
Post #1400936
Posted Tuesday, January 29, 2013 1:08 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 11, 2014 1:01 PM
Points: 2, Visits: 176
Any updates to this thread? We just received this error on a SQL 2008 R2 server here in our environment.
Post #1413283
Posted Friday, February 8, 2013 2:50 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, December 4, 2014 4:37 AM
Points: 36, Visits: 244
I've has this message 4 times in the past month on a SQL2008 R2 server. No performance issues so it seems pretty harmless.
Post #1417543
Posted Thursday, March 7, 2013 11:26 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Friday, August 1, 2014 6:40 PM
Points: 712, Visits: 653
Error msg - Failure to calculate super-latch promotion threshold - also known as Sub Latch. - Supporting article posted back in 09

http://blogs.msdn.com/b/psssql/archive/2010/03/24/how-it-works-bob-dorr-s-sql-server-i-o-presentation.aspx


Sub-latch is also referred to as super latch. These are only used for data cache page latches. They are designed to reduce the latching contention on hot pages. For example if you have a lookup table that is only a few pages in size but used by 100s of queries per second that SH latch activity is aggressive to protect the page. When SQL Server detects high rates of SH latch activity for a sustained period a buffer latch is PROMOTED to a sub-latch. A sub-latch partitions a single latch into an array of latch structures per logical CPU. In doing so the worker (always assigned to a specific CPU) only needs to acquire a SH on the sub-latch assigned to the local scheduler. This avoids interlocked activity and cache line invalidations across all physical CPUs. The acquiring of an SH sub-latch resource uses less resources and scales access to hot pages better.


Bleeding Edge - just means alot of sleepless nights
Post #1428163
Posted Monday, August 26, 2013 11:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 25, 2014 8:46 AM
Points: 2, Visits: 115
I just got this error message also on one of my servers. It is also 2008 R2 with SP2, but has had SP2 for a while now.


Post #1488472
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse