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

High percent signal waits with very low cpu usage Expand / Collapse
Author
Message
Posted Friday, November 15, 2013 8:31 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 17, 2014 8:05 AM
Points: 1,069, Visits: 421
I am trying to find out what could be causing this issue. Why would we be waiting on cpu when its barely being used. Signal waits are varying from 35 to 55% and cpu usage is only at 5% usage.

We are using Windows Server 2012 with SQl Server 2012 Standard edition with cpu5. There are 3 instances on the server each with max memory 50gb memory and the server has a total of 190gb memory. The machine is a 12 core machine with hyperthreading enabled. What types of things should I be looking into.

thanks for any insight. And let me know if you need additional information to help.
Post #1514750
Posted Friday, November 15, 2013 8:59 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 7:31 AM
Points: 4,472, Visits: 6,402
1) exactly what query are you using to identify the signal waits (and waits in general)? My guess is something like Glenn Berry's which is since server uptime or last reset, in which case you will be tracking stuff during all your batch operations such as data loads, reindexing, stats updates, checkdb, etc, which could be meaningless for your operational needs.

2) what are other high waits?

3) do you have any affinity settings other than default?

4) are these virtualized servers by any chance?

5) is anyone complaining about poor performance?

6) there are some very significant bug fixes in SP1 through CU6 (current highest build). I strongly recommend you try to upgrade to that.


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1514760
Posted Friday, November 15, 2013 10:31 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 17, 2014 8:05 AM
Points: 1,069, Visits: 421
We actually use Confio's Ignite when I am looking at resources. I have attached a screenshot. The affinity is set to the defaults. No virtuals and no performance complaints. Just very odd behavior. It seems to not being using the cpu on the box.



  Post Attachments 
11-15-2013 9-27-42 AM.png (40 views, 287.53 KB)
Post #1514798
Posted Saturday, November 16, 2013 8:24 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 7:31 AM
Points: 4,472, Visits: 6,402
Well, I think you are correct - it does seem to be odd behavior. Unfortunately it is so odd that I cannot offer any insight without being on the box. None of the usual suspects come to mind ... sorry!

Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1514924
Posted Wednesday, December 4, 2013 2:20 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 17, 2014 3:03 PM
Points: 101, Visits: 186
For what it's worth, I ran across your post while looking into the same issue and almost the same hardware.

I have no performance issues, so until I can discover a definitive answer I have chosen to interpret it to mean that the high signal waits as a percentage means that the CPU load is extremely low, and therefore a high percentage - as opposed to a high absolute number like 50000 seconds - just means that when compared to the overall number of waits, that signal waits are the highest as a percentage of a very low value. 20% of 1,000,000 is a lot, but 20% of 100 is not.

Having said that, I continue to look for a better explanation.



Post #1519787
Posted Wednesday, December 4, 2013 2:25 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, November 17, 2014 8:05 AM
Points: 1,069, Visits: 421
Thank you for the response. That does somewhat make sense. But I have still been researching as well and haven't come across any other explanations.
Post #1519789
Posted Wednesday, December 4, 2013 2:28 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 17, 2014 3:03 PM
Points: 101, Visits: 186
I intend to find the absolute value of all waits for the same period and see what the % of signal waits amounts to to get a better feel for the impact.


Post #1519790
Posted Tuesday, October 14, 2014 3:11 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, December 19, 2014 11:14 AM
Points: 2, Visits: 201
I'm facing the same issue. And, oddly enough, it is showing the same signal waits in Ignite.
Post #1625609
Posted Tuesday, October 14, 2014 3:48 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Thursday, December 18, 2014 9:50 AM
Points: 477, Visits: 1,053
Do you see any performance issues or complaints from your users other than it displaying in monitoring. ? If so I would recommend you do performance analysis using wait_stats and see if there is any bottlenecks on CPU. It is also little tricky when we have multiple instances on the same box, I would recommend to check the same from Ignite for other 2 instances and see how they look too.


--SQLFRNDZ
Post #1625621
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse