Once we fixed this issue of bottlenecks, we ended up on a very different issue where we had lots of runnable SPID and CPU was still underutilizing.
I eventually expressed them it is possible to detect CPU pressure with Wait Statistics. We explained to them my method during the Health Check.
I wrote a blog post about SQL SERVER – Best Value for Max Worker Count, after reading this blog post, I have received lots of emails.
We started working with my Comprehensive Database Performance Health Check service and found very interesting details from the server cache.
Question received via email: The question was about is there any way to know how many rows each thread execute in parallel operations.
Comprehensive Database Performance Health Check Client sent me an SOS message for help . The entire issue was about Page and Row level compression.