I have several queries that have a high duration (3,000 ms) and much lower
CPU values (300 ms). Is this ALWAYS an indicator of IO performance problems,
or could it be indicating other factors as well?
>>> On 11/27/2006 at 9:58 AM, in message
<ABFCA63C-E4D6-44B2-AECD-B8435E5F12E2@.microsoft.com>,
Dan<Dan@.discussions.microsoft.com> wrote:
> I have several queries that have a high duration (3,000 ms) and much
> lower
> CPU values (300 ms). Is this ALWAYS an indicator of IO performance
> problems,
> or could it be indicating other factors as well?
It could be other factors. For instance, a machine that is swapping or
has too little memory would do this too.
|||What would be the next steps in diagnosis?
"Joel Maslak" wrote:
> <ABFCA63C-E4D6-44B2-AECD-B8435E5F12E2@.microsoft.com>,
> Dan<Dan@.discussions.microsoft.com> wrote:
>
> It could be other factors. For instance, a machine that is swapping or
> has too little memory would do this too.
>
|||It is possible that the query is being blocked by another process. Also,
that query could be used by an app that does much work between retrieving
each row. The duration includes the time it takes to retrieve the last row.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:ABFCA63C-E4D6-44B2-AECD-B8435E5F12E2@.microsoft.com...
I have several queries that have a high duration (3,000 ms) and much lower
CPU values (300 ms). Is this ALWAYS an indicator of IO performance problems,
or could it be indicating other factors as well?
No comments:
Post a Comment