The avg wait is 0.0181 seconds. That does not look like an issue to solve.
Are you having a problem of some kind?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Run the wait stats SQL from https://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/ got:
wait type: SOS_SCHEDULER_YIELD
Wait_S: 90611.23
Resource_S: 3.6
Signal_S: 90607.63
WaitCount: 4994846
Percentage: 90.33
AvgWait_S: 0.0181
AvgRes_S: 0.0000
AvgSig_S: 0.0181
Please advise if we do need more CPU or SQL tuning.
Thanks,
Sky
The avg wait is 0.0181 seconds. That does not look like an issue to solve.
Are you having a problem of some kind?
That's a question we cannot answer, because it all depends on the requirements. If there is a requirements that says that you must be able to process N operations (as defined by whatever your application is for) per minute, and in your test show that you are only able to process N/2, then you have something to work with. On the other hand, if you are able to process 2*N operations, just be happy and smile. Yes, it may still be that the system can be tuned, but do you think your boss/client will agree to spend money on that when the test passes with flying colours?
The wait stats is only of interest if you have determined that you need to do better.