| John Bell 2006-12-04, 7:12 pm |
| Hi Paul
With performance monitor you have to watch out for the scale, it may be
clearer to look at the average, last, and max values in the middle of
the screen, below the graph. In general a maximum value would be 2*No
of Discs. This is the number of requests waiting on the disc to either
write/read, the counters can be views separately as well, there are
also current and average counters. If something is queuing to
write/read from disc it is waiting for the resource therefore slowing
the application down. In perfom there is an explain button that gives a
short description of the counter you select, which may help.
A couple of URLs
http://msdn2.microsoft.com/en-us/library/ms175903.aspx#
http://msdn2.microsoft.com/en-us/library/aa226166(SQL.70).aspx
http://www.sql-server-performance.c...st_3_pmlogs.asp
John
Paul Johnston wrote:[color=darkred
]
> Hi all,
>
> Many thanks for your replies. You are correct memory is not the real
> issue. It could be that we have i/o bottleneck elsewhere.
>
> According to the performance monitor our average disk queue length is
> at max most of the time. I have no idea what this means. Could
> someone please explain the significance, if any, of this performance
> counter.
>
> Thanks
>
> Paul.
>
> Gina Auer wrote:
|