Author vstinner
Recipients ammar2, giampaolo.rodola, jkloth, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-07-16.09:26:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531733201.21.0.56676864532.issue34060@psf.upfronthosting.co.za>
In-reply-to
Content
https://docs.microsoft.com/en-us/sql/relational-databases/performance-monitor/monitor-cpu-usage?view=sql-server-2017

Processor Queue Length:

Corresponds to the number of threads waiting for processor time. A processor bottleneck develops when threads of a process require more processor cycles than are available. If more than a few processes attempt to utilize the processor's time, you might need to install a faster processor. Or, if you have a multiprocessor system, you could add a processor.

When you examine processor usage, consider the type of work that the instance of SQL Server performs. If SQL Server performs many calculations, such as queries involving aggregates or memory-bound queries that require no disk I/O, 100 percent of the processor's time can be used. If this causes the performance of other applications to suffer, try changing the workload. For example, dedicate the computer to running the instance of SQL Server.

Usage rates around 100 percent, where many client requests are being processed, may indicate that processes are queuing up, waiting for processor time, and causing a bottleneck. Resolve the problem by adding faster processors.

--

Is it exactly the same thing on Unix (load average)? If not, I would prefer to use a different name in regrtest and "loadavg". Maybe "PQL avg"?

What is the impact of the number of CPUs on this value?
History
Date User Action Args
2018-07-16 09:26:41vstinnersetrecipients: + vstinner, paul.moore, giampaolo.rodola, tim.golden, jkloth, zach.ware, steve.dower, ammar2
2018-07-16 09:26:41vstinnersetmessageid: <1531733201.21.0.56676864532.issue34060@psf.upfronthosting.co.za>
2018-07-16 09:26:41vstinnerlinkissue34060 messages
2018-07-16 09:26:41vstinnercreate