We have a "chatty" application that makes a lot of sub-5ms calls to the database.
Everything is running as maxdop=1 on a 2 core dev system.
I only just noticed that profiler is reporting a lot of these calls, but not all of them, as having more CPU time than duration!
Why would that be?
There are NO transactions showing any CPU numbers between 0 and 15ms even though the duration times are at every possible point in between.
So, two possible explanations occur to me. Either, there is a minimum CPU quantum report in profiler, or else there is some overhead activity per RPC or batch, that may incur a quantum of CPU *and* violates the system maxdop setting!
Anyone know what the truth might be?
Thanks,
Josh