G
Guest
Hi All
Im trying to diagnose a slow running issue with a ProLiant ML370 G2 W2K
(SP4) file and print server, the main complaint from users is long delays in
opening / saving documents (30-60 sec to open a small word doc for example)
and slow running of databases.
Ive been searching for the root cause and noticed that the Average Disk
Queue Length perfmon graph goes absolutely haywire on both drive arrays,
peaking up in the millions(!) for a second or two then immediately coming
back down again to zero, then repeating this continuiously. From what Ive
read Microsoft say this queue should generally be between 0 and 10 (1.5x the
number of HDD spindles in the array?) and this is the behaviour Ive seen on
our other servers, so I do believe that something is going wrong somewhere on
this server.
Because its doing it on both arrays (c: logical drive is 2x9Gb mirrored, d:
is 4x36Gb RAID5), we concluded it may be an issue with the RAID controller so
had that swapped out, but that has not helped.
It still smells of a hardware issue to me but if it is, it must be further
up the chain than the RAID controller assuming one disk fault would not cause
this on BOTH arrays? So Before we swap anything else out I was hoping that
you guys may be able to give some inspiration on what may be causing this or
things to try?
thanks
Chris
Im trying to diagnose a slow running issue with a ProLiant ML370 G2 W2K
(SP4) file and print server, the main complaint from users is long delays in
opening / saving documents (30-60 sec to open a small word doc for example)
and slow running of databases.
Ive been searching for the root cause and noticed that the Average Disk
Queue Length perfmon graph goes absolutely haywire on both drive arrays,
peaking up in the millions(!) for a second or two then immediately coming
back down again to zero, then repeating this continuiously. From what Ive
read Microsoft say this queue should generally be between 0 and 10 (1.5x the
number of HDD spindles in the array?) and this is the behaviour Ive seen on
our other servers, so I do believe that something is going wrong somewhere on
this server.
Because its doing it on both arrays (c: logical drive is 2x9Gb mirrored, d:
is 4x36Gb RAID5), we concluded it may be an issue with the RAID controller so
had that swapped out, but that has not helped.
It still smells of a hardware issue to me but if it is, it must be further
up the chain than the RAID controller assuming one disk fault would not cause
this on BOTH arrays? So Before we swap anything else out I was hoping that
you guys may be able to give some inspiration on what may be causing this or
things to try?
thanks
Chris