Showing posts with label disk. Show all posts
Showing posts with label disk. Show all posts

Monday, February 13, 2012

%Disk Time value over 100

Hello!
I have collected counters using perfmon from our Production SQL Server. I
have noticed that %Disk Time counter averaging 111 with maximum value being
2249 for particular drive. I was wondering how I detect whether this value
indicates a bottleneck. Drive in question is RAID 10. Is there conversion
formula I should use?
I know that value over 60 indicates a potential problem. Average Disk Queue
lenght is 1 which means to me that disk is OK. I am confused by high %Disk
Time value.
Any advice is appreciated,
Igor
Used 100 - %disk idle time to get your utilization.
"imarchenko" wrote:

> Hello!
> I have collected counters using perfmon from our Production SQL Server. I
> have noticed that %Disk Time counter averaging 111 with maximum value being
> 2249 for particular drive. I was wondering how I detect whether this value
> indicates a bottleneck. Drive in question is RAID 10. Is there conversion
> formula I should use?
> I know that value over 60 indicates a potential problem. Average Disk Queue
> lenght is 1 which means to me that disk is OK. I am confused by high %Disk
> Time value.
>
> Any advice is appreciated,
> Igor
>
>
|||%Disk time is a useless counter on high-end IO systems. It was designed for
sequential command IO systems, not current SCSI systems that support Command
Tag Queuing or the new SATA Native Command Queuing options. These are the
device-level commands that support scatter-gather IO. Short description is
that they full-duplex command and response for IO. The device can queue a
large number of IO requests, sort them optimally, and respond to them
asychronously and asequentially. RAID subsystems further reduced the
effectiveness of this counter buy abstracting a large number of physical
devices into one logical device presented to the OS..
I use Physical disk | Disk Read Bytes/sec, Disk Write Bytes/sec, Disk
Reads/sec, Disk Writes/sec, and Disk Queue Length to determine if I am IO
bound. Of course, you need to know the maximum capabilities of your IO
subsystem to use these numbers effectively. But since you benchmarked the
IO system with IOMeter when you built the server that is an easy comparison.

Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eKaIHNaqFHA.4044@.TK2MSFTNGP09.phx.gbl...
> Hello!
> I have collected counters using perfmon from our Production SQL Server.
> I have noticed that %Disk Time counter averaging 111 with maximum value
> being 2249 for particular drive. I was wondering how I detect whether this
> value indicates a bottleneck. Drive in question is RAID 10. Is there
> conversion formula I should use?
> I know that value over 60 indicates a potential problem. Average Disk
> Queue lenght is 1 which means to me that disk is OK. I am confused by high
> %Disk Time value.
>
> Any advice is appreciated,
> Igor
>
|||Jeffrey,
Thanks a lot!
Igor
"Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
message news:22B02C35-4D78-47A1-B273-88ED2F5EDACA@.microsoft.com...[vbcol=seagreen]
> Used 100 - %disk idle time to get your utilization.
> "imarchenko" wrote:
|||Thanks, Geoff. I really appreciate your elaborate reply.
Igor
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:eSP65saqFHA.272@.TK2MSFTNGP15.phx.gbl...
> %Disk time is a useless counter on high-end IO systems. It was designed
> for sequential command IO systems, not current SCSI systems that support
> Command Tag Queuing or the new SATA Native Command Queuing options. These
> are the device-level commands that support scatter-gather IO. Short
> description is that they full-duplex command and response for IO. The
> device can queue a large number of IO requests, sort them optimally, and
> respond to them asychronously and asequentially. RAID subsystems further
> reduced the effectiveness of this counter buy abstracting a large number
> of physical devices into one logical device presented to the OS..
> I use Physical disk | Disk Read Bytes/sec, Disk Write Bytes/sec, Disk
> Reads/sec, Disk Writes/sec, and Disk Queue Length to determine if I am IO
> bound. Of course, you need to know the maximum capabilities of your IO
> subsystem to use these numbers effectively. But since you benchmarked the
> IO system with IOMeter when you built the server that is an easy
> comparison.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eKaIHNaqFHA.4044@.TK2MSFTNGP09.phx.gbl...
>

%Disk Time value over 100

Hello!
I have collected counters using perfmon from our Production SQL Server. I
have noticed that %Disk Time counter averaging 111 with maximum value being
2249 for particular drive. I was wondering how I detect whether this value
indicates a bottleneck. Drive in question is RAID 10. Is there conversion
formula I should use?
I know that value over 60 indicates a potential problem. Average Disk Queue
lenght is 1 which means to me that disk is OK. I am confused by high %Disk
Time value.
Any advice is appreciated,
IgorUsed 100 - %disk idle time to get your utilization.
"imarchenko" wrote:

> Hello!
> I have collected counters using perfmon from our Production SQL Server.
I
> have noticed that %Disk Time counter averaging 111 with maximum value bein
g
> 2249 for particular drive. I was wondering how I detect whether this value
> indicates a bottleneck. Drive in question is RAID 10. Is there conversion
> formula I should use?
> I know that value over 60 indicates a potential problem. Average Disk Queu
e
> lenght is 1 which means to me that disk is OK. I am confused by high %Disk
> Time value.
>
> Any advice is appreciated,
> Igor
>
>|||%Disk time is a useless counter on high-end IO systems. It was designed for
sequential command IO systems, not current SCSI systems that support Command
Tag Queuing or the new SATA Native Command Queuing options. These are the
device-level commands that support scatter-gather IO. Short description is
that they full-duplex command and response for IO. The device can queue a
large number of IO requests, sort them optimally, and respond to them
asychronously and asequentially. RAID subsystems further reduced the
effectiveness of this counter buy abstracting a large number of physical
devices into one logical device presented to the OS..
I use Physical disk | Disk Read Bytes/sec, Disk Write Bytes/sec, Disk
Reads/sec, Disk Writes/sec, and Disk Queue Length to determine if I am IO
bound. Of course, you need to know the maximum capabilities of your IO
subsystem to use these numbers effectively. But since you benchmarked the
IO system with IOMeter when you built the server that is an easy comparison.

Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eKaIHNaqFHA.4044@.TK2MSFTNGP09.phx.gbl...
> Hello!
> I have collected counters using perfmon from our Production SQL Server.
> I have noticed that %Disk Time counter averaging 111 with maximum value
> being 2249 for particular drive. I was wondering how I detect whether this
> value indicates a bottleneck. Drive in question is RAID 10. Is there
> conversion formula I should use?
> I know that value over 60 indicates a potential problem. Average Disk
> Queue lenght is 1 which means to me that disk is OK. I am confused by high
> %Disk Time value.
>
> Any advice is appreciated,
> Igor
>

%Disk Time value over 100

Hello!
I have collected counters using perfmon from our Production SQL Server. I
have noticed that %Disk Time counter averaging 111 with maximum value being
2249 for particular drive. I was wondering how I detect whether this value
indicates a bottleneck. Drive in question is RAID 10. Is there conversion
formula I should use?
I know that value over 60 indicates a potential problem. Average Disk Queue
lenght is 1 which means to me that disk is OK. I am confused by high %Disk
Time value.
Any advice is appreciated,
IgorUsed 100 - %disk idle time to get your utilization.
"imarchenko" wrote:
> Hello!
> I have collected counters using perfmon from our Production SQL Server. I
> have noticed that %Disk Time counter averaging 111 with maximum value being
> 2249 for particular drive. I was wondering how I detect whether this value
> indicates a bottleneck. Drive in question is RAID 10. Is there conversion
> formula I should use?
> I know that value over 60 indicates a potential problem. Average Disk Queue
> lenght is 1 which means to me that disk is OK. I am confused by high %Disk
> Time value.
>
> Any advice is appreciated,
> Igor
>
>|||%Disk time is a useless counter on high-end IO systems. It was designed for
sequential command IO systems, not current SCSI systems that support Command
Tag Queuing or the new SATA Native Command Queuing options. These are the
device-level commands that support scatter-gather IO. Short description is
that they full-duplex command and response for IO. The device can queue a
large number of IO requests, sort them optimally, and respond to them
asychronously and asequentially. RAID subsystems further reduced the
effectiveness of this counter buy abstracting a large number of physical
devices into one logical device presented to the OS..
I use Physical disk | Disk Read Bytes/sec, Disk Write Bytes/sec, Disk
Reads/sec, Disk Writes/sec, and Disk Queue Length to determine if I am IO
bound. Of course, you need to know the maximum capabilities of your IO
subsystem to use these numbers effectively. But since you benchmarked the
IO system with IOMeter when you built the server that is an easy comparison.
:)
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eKaIHNaqFHA.4044@.TK2MSFTNGP09.phx.gbl...
> Hello!
> I have collected counters using perfmon from our Production SQL Server.
> I have noticed that %Disk Time counter averaging 111 with maximum value
> being 2249 for particular drive. I was wondering how I detect whether this
> value indicates a bottleneck. Drive in question is RAID 10. Is there
> conversion formula I should use?
> I know that value over 60 indicates a potential problem. Average Disk
> Queue lenght is 1 which means to me that disk is OK. I am confused by high
> %Disk Time value.
>
> Any advice is appreciated,
> Igor
>|||Jeffrey,
Thanks a lot!
Igor
"Jeffrey K. Ericson" <JeffreyKEricson@.discussions.microsoft.com> wrote in
message news:22B02C35-4D78-47A1-B273-88ED2F5EDACA@.microsoft.com...
> Used 100 - %disk idle time to get your utilization.
> "imarchenko" wrote:
>> Hello!
>> I have collected counters using perfmon from our Production SQL
>> Server. I
>> have noticed that %Disk Time counter averaging 111 with maximum value
>> being
>> 2249 for particular drive. I was wondering how I detect whether this
>> value
>> indicates a bottleneck. Drive in question is RAID 10. Is there conversion
>> formula I should use?
>> I know that value over 60 indicates a potential problem. Average Disk
>> Queue
>> lenght is 1 which means to me that disk is OK. I am confused by high
>> %Disk
>> Time value.
>>
>> Any advice is appreciated,
>> Igor
>>|||Thanks, Geoff. I really appreciate your elaborate reply.
Igor
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:eSP65saqFHA.272@.TK2MSFTNGP15.phx.gbl...
> %Disk time is a useless counter on high-end IO systems. It was designed
> for sequential command IO systems, not current SCSI systems that support
> Command Tag Queuing or the new SATA Native Command Queuing options. These
> are the device-level commands that support scatter-gather IO. Short
> description is that they full-duplex command and response for IO. The
> device can queue a large number of IO requests, sort them optimally, and
> respond to them asychronously and asequentially. RAID subsystems further
> reduced the effectiveness of this counter buy abstracting a large number
> of physical devices into one logical device presented to the OS..
> I use Physical disk | Disk Read Bytes/sec, Disk Write Bytes/sec, Disk
> Reads/sec, Disk Writes/sec, and Disk Queue Length to determine if I am IO
> bound. Of course, you need to know the maximum capabilities of your IO
> subsystem to use these numbers effectively. But since you benchmarked the
> IO system with IOMeter when you built the server that is an easy
> comparison. :)
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eKaIHNaqFHA.4044@.TK2MSFTNGP09.phx.gbl...
>> Hello!
>> I have collected counters using perfmon from our Production SQL Server.
>> I have noticed that %Disk Time counter averaging 111 with maximum value
>> being 2249 for particular drive. I was wondering how I detect whether
>> this value indicates a bottleneck. Drive in question is RAID 10. Is there
>> conversion formula I should use?
>> I know that value over 60 indicates a potential problem. Average Disk
>> Queue lenght is 1 which means to me that disk is OK. I am confused by
>> high %Disk Time value.
>>
>> Any advice is appreciated,
>> Igor
>>
>

%disk time > 2500

Is the %disk time > 2500 bad ? What does that mean ? My pages/sec seem to be
low ..around 0 with a few spikes here and there..so why is the %disk time
high ?
ThanksHi,
%disk time > 2500 , are you saying that your disk is running at 2500%, if
you are I want one of those disk :)
Can you tell me if you are using a software RAID 5 config? If so this might
explain the numbers. If you are using a software raid try dividing this
number by the number of disks. Although thinking a bit more I doubt
software RAID would explain the figure.
Basically PhysicalDisk:% Disktime shows how busy each disk is. long period
of busy times say over 50% for 10 minutes indicates problems (too many
writes/reads , slow disk) So a figure of 2500 is really saying something.
You should look to other counters like %disk read time %disk write time and
Avg Disk queue length to see where the issues are . If this activity is not
caused by paging then you have a very very busy machine.
I hope this helps
regards
Greg O MCSD
http://www.ag-software.com/ags_scribe_index.asp. SQL Scribe Documentation
Builder, the quickest way to document your database
http://www.ag-software.com/ags_SSEPE_index.asp. AGS SQL Server Extended
Property Extended properties manager for SQL 2000
http://www.ag-software.com/IconExtractionProgram.asp. Free icon extraction
program
http://www.ag-software.com. Free programming tools
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:O30Ol8LWDHA.392@.TK2MSFTNGP11.phx.gbl...
> Is the %disk time > 2500 bad ? What does that mean ? My pages/sec seem to
be
> low ..around 0 with a few spikes here and there..so why is the %disk time
> high ?
> Thanks
>

% Disk Time counter

I'm monitoring our database server and the "% Disk Time" counter in the
"Physical Disk" object is confusing me. Over a 24 hour period I'm getting
Min = 0.15, Max = 20269 and Average = 136. I am monitoring the database
drive itself not transaction logs and the database is on a RAID 10 SAN. Can
anybody shed any light on how I should read these figures?
thanks
Gav% Disk Time is more or less meaningless. It's just (average disk queue
length) * 100. Better to monitor the queue length itself, and correlate
that number with counters like Avg Seconds/Read and Avg Seconds/Write. A
queue of 202 may indicate a problem, but you really need those average
counters to find out how bad things are really getting.
Adam Machanic
SQL Server MVP - http://sqlblog.com
Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220
"Gav" <gav@.nospam.com> wrote in message
news:uTHfuPy8HHA.1164@.TK2MSFTNGP02.phx.gbl...
> I'm monitoring our database server and the "% Disk Time" counter in the
> "Physical Disk" object is confusing me. Over a 24 hour period I'm getting
> Min = 0.15, Max = 20269 and Average = 136. I am monitoring the database
> drive itself not transaction logs and the database is on a RAID 10 SAN.
> Can anybody shed any light on how I should read these figures?
> thanks
> Gav
>|||Also:
For calculation, you need to divide the test result to your physical disks'
count. (If you selected "Total_" object instead of a specific disk.)
For example there could be 8 disks on your SAN then you need to divide the
result to 8 to find the correct analysis.
--
Ekrem Önsoy
"Gav" <gav@.nospam.com> wrote in message
news:uTHfuPy8HHA.1164@.TK2MSFTNGP02.phx.gbl...
> I'm monitoring our database server and the "% Disk Time" counter in the
> "Physical Disk" object is confusing me. Over a 24 hour period I'm getting
> Min = 0.15, Max = 20269 and Average = 136. I am monitoring the database
> drive itself not transaction logs and the database is on a RAID 10 SAN.
> Can anybody shed any light on how I should read these figures?
> thanks
> Gav
>

% Disk Time (Perfmon)

I have a Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition on a SAN. What units are the %Disk
Time measured in from Perfmon?
Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
Time) ?
Please help me with these questions.
Thanks,
MikeMike
This counter measured how busy a physical array is. In general it should be
less 55% otherwise you probably jave IO bottleneck.
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike|||I don't tend to agree with that advice.
On it's own
<<
'%Disk Time
Is not a very reliable indicator of an IO bottleneck. You could easily have
a bottleneck if this counter is much lower than 55%. You might NOT have a
bottleneck if this counter is 55% or higher.
There are many, many more counters which you should take a look. You need to
take a look at queue lenght, wait times for disk transfers, time it takes
per read and write. In addition, there are a host of other counters
specific to your SAN that you should take a look at.
Unfortunately, I'm running a bit late right now and I don't have time to
write a long message. Tom Davidson from MS has a nice article in SQL Server
Magazine that dicusses some of these counters. I believe it might also be on
MSDN. It shouldn't be too hard to track down if you search by his name on
each site.
--
Brian Moran
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> Mike
> This counter measured how busy a physical array is. In general it should
be
> less 55% otherwise you probably jave IO bottleneck.
>
>
> "Mike" <anonymous@.discussions.microsoft.com> wrote in message
> news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
> >
> > I have a Windows 2000 Advanced Server with SQL Server 2000
> > Enterprise Edition on a SAN. What units are the %Disk
> > Time measured in from Perfmon?
> >
> > Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> > Time) ?
> >
> > Please help me with these questions.
> >
> > Thanks,
> >
> > Mike
>|||Brian
First of all i have said 'probably'
Secondly if you have this counter higher than 55% for continuous periods
(let me say 15 min)then your SQL Server
may be experiencing an I/O bottleneck.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> I don't tend to agree with that advice.
> On it's own
> <<
> '%Disk Time
> >>
> Is not a very reliable indicator of an IO bottleneck. You could easily
have
> a bottleneck if this counter is much lower than 55%. You might NOT have a
> bottleneck if this counter is 55% or higher.
> There are many, many more counters which you should take a look. You need
to
> take a look at queue lenght, wait times for disk transfers, time it takes
> per read and write. In addition, there are a host of other counters
> specific to your SAN that you should take a look at.
>
> Unfortunately, I'm running a bit late right now and I don't have time to
> write a long message. Tom Davidson from MS has a nice article in SQL
Server
> Magazine that dicusses some of these counters. I believe it might also be
on
> MSDN. It shouldn't be too hard to track down if you search by his name on
> each site.
> --
> Brian Moran
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> > Mike
> > This counter measured how busy a physical array is. In general it should
> be
> > less 55% otherwise you probably jave IO bottleneck.
> >
> >
> >
> >
> >
> > "Mike" <anonymous@.discussions.microsoft.com> wrote in message
> > news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
> > >
> > > I have a Windows 2000 Advanced Server with SQL Server 2000
> > > Enterprise Edition on a SAN. What units are the %Disk
> > > Time measured in from Perfmon?
> > >
> > > Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> > > Time) ?
> > >
> > > Please help me with these questions.
> > >
> > > Thanks,
> > >
> > > Mike
> >
> >
>

% Disk Time (Perfmon)

I have a Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition on a SAN. What units are the %Disk
Time measured in from Perfmon?
Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
Time) ?
Please help me with these questions.
Thanks,
Mike
Mike
This counter measured how busy a physical array is. In general it should be
less 55% otherwise you probably jave IO bottleneck.
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
|||I don't tend to agree with that advice.
On it's own
<<
'%Disk Time[vbcol=seagreen]
Is not a very reliable indicator of an IO bottleneck. You could easily have
a bottleneck if this counter is much lower than 55%. You might NOT have a
bottleneck if this counter is 55% or higher.
There are many, many more counters which you should take a look. You need to
take a look at queue lenght, wait times for disk transfers, time it takes
per read and write. In addition, there are a host of other counters
specific to your SAN that you should take a look at.
Unfortunately, I'm running a bit late right now and I don't have time to
write a long message. Tom Davidson from MS has a nice article in SQL Server
Magazine that dicusses some of these counters. I believe it might also be on
MSDN. It shouldn't be too hard to track down if you search by his name on
each site.
Brian Moran
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> Mike
> This counter measured how busy a physical array is. In general it should
be
> less 55% otherwise you probably jave IO bottleneck.
>
>
> "Mike" <anonymous@.discussions.microsoft.com> wrote in message
> news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
>
|||Brian
First of all i have said 'probably'
Secondly if you have this counter higher than 55% for continuous periods
(let me say 15 min)then your SQL Server
may be experiencing an I/O bottleneck.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> I don't tend to agree with that advice.
> On it's own
> <<
> '%Disk Time
> Is not a very reliable indicator of an IO bottleneck. You could easily
have
> a bottleneck if this counter is much lower than 55%. You might NOT have a
> bottleneck if this counter is 55% or higher.
> There are many, many more counters which you should take a look. You need
to
> take a look at queue lenght, wait times for disk transfers, time it takes
> per read and write. In addition, there are a host of other counters
> specific to your SAN that you should take a look at.
>
> Unfortunately, I'm running a bit late right now and I don't have time to
> write a long message. Tom Davidson from MS has a nice article in SQL
Server
> Magazine that dicusses some of these counters. I believe it might also be
on
> MSDN. It shouldn't be too hard to track down if you search by his name on
> each site.
> --
> Brian Moran
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> be
>

% Disk Time (Perfmon)

I have a Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition on a SAN. What units are the %Disk
Time measured in from Perfmon?
Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
Time) ?
Please help me with these questions.
Thanks,
MikeMike
This counter measured how busy a physical array is. In general it should be
less 55% otherwise you probably jave IO bottleneck.
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike|||I don't tend to agree with that advice.
On it's own
<<
'%Disk Time
Is not a very reliable indicator of an IO bottleneck. You could easily have
a bottleneck if this counter is much lower than 55%. You might NOT have a
bottleneck if this counter is 55% or higher.
There are many, many more counters which you should take a look. You need to
take a look at queue lenght, wait times for disk transfers, time it takes
per read and write. In addition, there are a host of other counters
specific to your SAN that you should take a look at.
Unfortunately, I'm running a bit late right now and I don't have time to
write a long message. Tom Davidson from MS has a nice article in SQL Server
Magazine that dicusses some of these counters. I believe it might also be on
MSDN. It shouldn't be too hard to track down if you search by his name on
each site.
--
Brian Moran
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Mike
> This counter measured how busy a physical array is. In general it should
be
> less 55% otherwise you probably jave IO bottleneck.
>
>
> "Mike" <anonymous@.discussions.microsoft.com> wrote in message
> news:c13201c47a1b$4db045c0$a401280a@.phx.gbl...
>|||Brian
First of all i have said 'probably'
Secondly if you have this counter higher than 55% for continuous periods
(let me say 15 min)then your SQL Server
may be experiencing an I/O bottleneck.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> I don't tend to agree with that advice.
> On it's own
> <<
> '%Disk Time
> Is not a very reliable indicator of an IO bottleneck. You could easily
have
> a bottleneck if this counter is much lower than 55%. You might NOT have a
> bottleneck if this counter is 55% or higher.
> There are many, many more counters which you should take a look. You need
to
> take a look at queue lenght, wait times for disk transfers, time it takes
> per read and write. In addition, there are a host of other counters
> specific to your SAN that you should take a look at.
>
> Unfortunately, I'm running a bit late right now and I don't have time to
> write a long message. Tom Davidson from MS has a nice article in SQL
Server
> Magazine that dicusses some of these counters. I believe it might also be
on
> MSDN. It shouldn't be too hard to track down if you search by his name on
> each site.
> --
> Brian Moran
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> be
>

% Disk Time

I have separate drives each SQL Server database:
database file (E
database transaction log (K
tempdb (M
database system files (F
My database % Disk Time: (Average = 2541, STDEV = 4316,
Maximum = 86770)
How is the % Disk Time measured?
The % Disk Time high at 55%?
Thanks,
__________________________________________________ _________
Brian
First of all i have said 'probably'
Secondly if you have this counter higher than 55% for
continuous periods
(let me say 15 min)then your SQL Server
may be experiencing an I/O bottleneck.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in
message
news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> I don't tend to agree with that advice.
> On it's own
> <<
> '%Disk Time
> Is not a very reliable indicator of an IO bottleneck.
You could easily
have
> a bottleneck if this counter is much lower than 55%. You
might NOT have a
> bottleneck if this counter is 55% or higher.
> There are many, many more counters which you should take
a look. You need
to
> take a look at queue lenght, wait times for disk
transfers, time it takes
> per read and write. In addition, there are a host of
other counters
> specific to your SAN that you should take a look at.
>
> Unfortunately, I'm running a bit late right now and I
don't have time to
> write a long message. Tom Davidson from MS has a nice
article in SQL
Server
> Magazine that dicusses some of these counters. I believe
it might also be
on
> MSDN. It shouldn't be too hard to track down if you
search by his name on[vbcol=seagreen]
> each site.
> --
> Brian Moran
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
general it should[vbcol=seagreen]
> be
I have a Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition on a SAN. What units are the %Disk
Time measured in from Perfmon?
Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
Time) ?
Please help me with these questions.
Thanks,
Mike
%Disk time is a bogus number and is useless for performance measurement. It
does not take into account asychronous I/O requests and cannot tell what the
real performance capability of an underlying RAID set may be. I prefer
using Transfers/sec, Read Bytes/sec and Write Bytes/sec, and Disk Queue
length to measure the performance of my disk subsystems. It is important
to take a few hours and benchmark your system with an I/O stress tool before
going live so you will know what your maximum capacities really are.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E
> database transaction log (K
> tempdb (M
> database system files (F
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> __________________________________________________ _________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> You could easily
> have
> might NOT have a
> a look. You need
> to
> transfers, time it takes
> other counters
> don't have time to
> article in SQL
> Server
> it might also be
> on
> search by his name on
> general it should
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>
|||That counter is pretty much useless in my opinion. I have seen this vary
greatly with the different types of hardware used. It's better to use the
Avg and current Disk queues instead. They give a much better view of how
your drives are able to handle the load. By the way are these drives
Logical or Physical?
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E
> database transaction log (K
> tempdb (M
> database system files (F
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> __________________________________________________ _________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> You could easily
> have
> might NOT have a
> a look. You need
> to
> transfers, time it takes
> other counters
> don't have time to
> article in SQL
> Server
> it might also be
> on
> search by his name on
> general it should
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>
|||I mostly use Average disk queue length... Any average disk queue length > 2
on a single spindle = bad.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E
> database transaction log (K
> tempdb (M
> database system files (F
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> __________________________________________________ _________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> You could easily
> have
> might NOT have a
> a look. You need
> to
> transfers, time it takes
> other counters
> don't have time to
> article in SQL
> Server
> it might also be
> on
> search by his name on
> general it should
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>

% Disk Time

I have separate drives each SQL Server database:
database file (E
database transaction log (K
tempdb (M
database system files (F
My database % Disk Time: (Average = 2541, STDEV = 4316,
Maximum = 86770)
How is the % Disk Time measured?
The % Disk Time high at 55%?
Thanks,
________________________________________
___________________
Brian
First of all i have said 'probably'
Secondly if you have this counter higher than 55% for
continuous periods
(let me say 15 min)then your SQL Server
may be experiencing an I/O bottleneck.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in
message
news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> I don't tend to agree with that advice.
> On it's own
> <<
> '%Disk Time
> Is not a very reliable indicator of an IO bottleneck.
You could easily
have
> a bottleneck if this counter is much lower than 55%. You
might NOT have a
> bottleneck if this counter is 55% or higher.
> There are many, many more counters which you should take
a look. You need
to
> take a look at queue lenght, wait times for disk
transfers, time it takes
> per read and write. In addition, there are a host of
other counters
> specific to your SAN that you should take a look at.
>
> Unfortunately, I'm running a bit late right now and I
don't have time to
> write a long message. Tom Davidson from MS has a nice
article in SQL
Server
> Magazine that dicusses some of these counters. I believe
it might also be
on
> MSDN. It shouldn't be too hard to track down if you
search by his name on[vbcol=seagreen]
> each site.
> --
> Brian Moran
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
general it should[vbcol=seagreen]
> be
I have a Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition on a SAN. What units are the %Disk
Time measured in from Perfmon?
Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
Time) ?
Please help me with these questions.
Thanks,
Mike%Disk time is a bogus number and is useless for performance measurement. It
does not take into account asychronous I/O requests and cannot tell what the
real performance capability of an underlying RAID set may be. I prefer
using Transfers/sec, Read Bytes/sec and Write Bytes/sec, and Disk Queue
length to measure the performance of my disk subsystems. It is important
to take a few hours and benchmark your system with an I/O stress tool before
going live so you will know what your maximum capacities really are.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E
> database transaction log (K
> tempdb (M
> database system files (F
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> ________________________________________
___________________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> You could easily
> have
> might NOT have a
> a look. You need
> to
> transfers, time it takes
> other counters
> don't have time to
> article in SQL
> Server
> it might also be
> on
> search by his name on
> general it should
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>|||That counter is pretty much useless in my opinion. I have seen this vary
greatly with the different types of hardware used. It's better to use the
Avg and current Disk queues instead. They give a much better view of how
your drives are able to handle the load. By the way are these drives
Logical or Physical?
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E
> database transaction log (K
> tempdb (M
> database system files (F
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> ________________________________________
___________________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> You could easily
> have
> might NOT have a
> a look. You need
> to
> transfers, time it takes
> other counters
> don't have time to
> article in SQL
> Server
> it might also be
> on
> search by his name on
> general it should
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>|||I mostly use Average disk queue length... Any average disk queue length > 2
on a single spindle = bad.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E
> database transaction log (K
> tempdb (M
> database system files (F
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> ________________________________________
___________________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> You could easily
> have
> might NOT have a
> a look. You need
> to
> transfers, time it takes
> other counters
> don't have time to
> article in SQL
> Server
> it might also be
> on
> search by his name on
> general it should
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>

% Disk Time

I have separate drives each SQL Server database:
database file (E:)
database transaction log (K:)
tempdb (M:)
database system files (F:)
My database % Disk Time: (Average = 2541, STDEV = 4316,
Maximum = 86770)
How is the % Disk Time measured?
The % Disk Time high at 55%?
Thanks,
___________________________________________________________
Brian
First of all i have said 'probably'
Secondly if you have this counter higher than 55% for
continuous periods
(let me say 15 min)then your SQL Server
may be experiencing an I/O bottleneck.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in
message
news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> I don't tend to agree with that advice.
>
> On it's own
> <<
> '%Disk Time
> >>
>
> Is not a very reliable indicator of an IO bottleneck.
You could easily
have
> a bottleneck if this counter is much lower than 55%. You
might NOT have a
> bottleneck if this counter is 55% or higher.
>
> There are many, many more counters which you should take
a look. You need
to
> take a look at queue lenght, wait times for disk
transfers, time it takes
> per read and write. In addition, there are a host of
other counters
> specific to your SAN that you should take a look at.
>
>
> Unfortunately, I'm running a bit late right now and I
don't have time to
> write a long message. Tom Davidson from MS has a nice
article in SQL
Server
> Magazine that dicusses some of these counters. I believe
it might also be
on
> MSDN. It shouldn't be too hard to track down if you
search by his name on
> each site.
> --
>
> Brian Moran
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> > Mike
> > This counter measured how busy a physical array is. In
general it should
> be
> > less 55% otherwise you probably jave IO bottleneck.
> >
> >
> >
I have a Windows 2000 Advanced Server with SQL Server 2000
Enterprise Edition on a SAN. What units are the %Disk
Time measured in from Perfmon?
Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
Time) ?
Please help me with these questions.
Thanks,
Mike%Disk time is a bogus number and is useless for performance measurement. It
does not take into account asychronous I/O requests and cannot tell what the
real performance capability of an underlying RAID set may be. I prefer
using Transfers/sec, Read Bytes/sec and Write Bytes/sec, and Disk Queue
length to measure the performance of my disk subsystems. It is important
to take a few hours and benchmark your system with an I/O stress tool before
going live so you will know what your maximum capacities really are.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E:)
> database transaction log (K:)
> tempdb (M:)
> database system files (F:)
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> ___________________________________________________________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > I don't tend to agree with that advice.
> >
> > On it's own
> > <<
> > '%Disk Time
> > >>
> >
> > Is not a very reliable indicator of an IO bottleneck.
> You could easily
> have
> > a bottleneck if this counter is much lower than 55%. You
> might NOT have a
> > bottleneck if this counter is 55% or higher.
> >
> > There are many, many more counters which you should take
> a look. You need
> to
> > take a look at queue lenght, wait times for disk
> transfers, time it takes
> > per read and write. In addition, there are a host of
> other counters
> > specific to your SAN that you should take a look at.
> >
> >
> > Unfortunately, I'm running a bit late right now and I
> don't have time to
> > write a long message. Tom Davidson from MS has a nice
> article in SQL
> Server
> > Magazine that dicusses some of these counters. I believe
> it might also be
> on
> > MSDN. It shouldn't be too hard to track down if you
> search by his name on
> > each site.
> > --
> >
> > Brian Moran
> >
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> > > Mike
> > > This counter measured how busy a physical array is. In
> general it should
> > be
> > > less 55% otherwise you probably jave IO bottleneck.
> > >
> > >
> > >
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>|||That counter is pretty much useless in my opinion. I have seen this vary
greatly with the different types of hardware used. It's better to use the
Avg and current Disk queues instead. They give a much better view of how
your drives are able to handle the load. By the way are these drives
Logical or Physical?
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E:)
> database transaction log (K:)
> tempdb (M:)
> database system files (F:)
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> ___________________________________________________________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > I don't tend to agree with that advice.
> >
> > On it's own
> > <<
> > '%Disk Time
> > >>
> >
> > Is not a very reliable indicator of an IO bottleneck.
> You could easily
> have
> > a bottleneck if this counter is much lower than 55%. You
> might NOT have a
> > bottleneck if this counter is 55% or higher.
> >
> > There are many, many more counters which you should take
> a look. You need
> to
> > take a look at queue lenght, wait times for disk
> transfers, time it takes
> > per read and write. In addition, there are a host of
> other counters
> > specific to your SAN that you should take a look at.
> >
> >
> > Unfortunately, I'm running a bit late right now and I
> don't have time to
> > write a long message. Tom Davidson from MS has a nice
> article in SQL
> Server
> > Magazine that dicusses some of these counters. I believe
> it might also be
> on
> > MSDN. It shouldn't be too hard to track down if you
> search by his name on
> > each site.
> > --
> >
> > Brian Moran
> >
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> > > Mike
> > > This counter measured how busy a physical array is. In
> general it should
> > be
> > > less 55% otherwise you probably jave IO bottleneck.
> > >
> > >
> > >
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>|||I mostly use Average disk queue length... Any average disk queue length > 2
on a single spindle = bad.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:192c01c47bea$40735340$a601280a@.phx.gbl...
> I have separate drives each SQL Server database:
> database file (E:)
> database transaction log (K:)
> tempdb (M:)
> database system files (F:)
> My database % Disk Time: (Average = 2541, STDEV = 4316,
> Maximum = 86770)
> How is the % Disk Time measured?
> The % Disk Time high at 55%?
> Thanks,
> ___________________________________________________________
> Brian
> First of all i have said 'probably'
> Secondly if you have this counter higher than 55% for
> continuous periods
> (let me say 15 min)then your SQL Server
>
> may be experiencing an I/O bottleneck.
> "Brian Moran" <brian@.solidqualitylearning.com> wrote in
> message
> news:%23r7TWIieEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > I don't tend to agree with that advice.
> >
> > On it's own
> > <<
> > '%Disk Time
> > >>
> >
> > Is not a very reliable indicator of an IO bottleneck.
> You could easily
> have
> > a bottleneck if this counter is much lower than 55%. You
> might NOT have a
> > bottleneck if this counter is 55% or higher.
> >
> > There are many, many more counters which you should take
> a look. You need
> to
> > take a look at queue lenght, wait times for disk
> transfers, time it takes
> > per read and write. In addition, there are a host of
> other counters
> > specific to your SAN that you should take a look at.
> >
> >
> > Unfortunately, I'm running a bit late right now and I
> don't have time to
> > write a long message. Tom Davidson from MS has a nice
> article in SQL
> Server
> > Magazine that dicusses some of these counters. I believe
> it might also be
> on
> > MSDN. It shouldn't be too hard to track down if you
> search by his name on
> > each site.
> > --
> >
> > Brian Moran
> >
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:u1rJ0yheEHA.3520@.TK2MSFTNGP10.phx.gbl...
> > > Mike
> > > This counter measured how busy a physical array is. In
> general it should
> > be
> > > less 55% otherwise you probably jave IO bottleneck.
> > >
> > >
> > >
> I have a Windows 2000 Advanced Server with SQL Server 2000
> Enterprise Edition on a SAN. What units are the %Disk
> Time measured in from Perfmon?
> Is the (% Disk Time E) = (Disk Time E) / (Total % Disk
> Time) ?
> Please help me with these questions.
> Thanks,
> Mike
>