October 17, 2014 at 8:54 am
Hi Experts,
High CPU usage of above 95% for hours will bring SQL Server down?
October 17, 2014 at 9:00 am
Not alone, no.
Is this related to http://www.sqlservercentral.com/Forums/Topic1625741-2799-1.aspx?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 17, 2014 at 9:05 am
No, it's http://www.sqlservercentral.com/Forums/FindPost1626609.aspx
Don't cross post please.
-- Gianluca Sartori
October 17, 2014 at 10:41 am
It's actually a new thread from a divergence on another thread.
I'd say you need to define "down." Can SQL Server sit there chugging away with CPU hovering near 100% for hours? Yes. Can this appear to be "down" because it's not accepting new connections, or the connections are running extremely slow, or the connections are all blocked because no sessions can get at the CPU? Yes. But for "down" is when the server is completely offline. Not just in a problematic state, but literally down, switched off. And no, by itself high CPU is unlikely to cause the server itself to go completely offline. It can sure do those other things though.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 17, 2014 at 11:08 am
High CPU over 95% on long time periods holds the possibility to go to 100% at times and then is the good probability for deadlocking.
I've read in a performance poster that max CPU bounds should be somewhere between 70-80%
Igor Micev,My blog: www.igormicev.com
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply