Server 2003 te disk...
 
Bildirimler
Hepsini Temizle

Server 2003 te disk performansını ölçme  

  RSS
Bt Expert
(@BtExpert)
Üye

Merhabalar,

Performance logs and alerts kısmında disklerin yazma ve okuma hızlarını darboğaz olup olmadığını anlayabilmek için adım adım neler yapmam gerektiğini yazabilirmisiniz? Alacağım değerler kaçı geçerse yükseltme yapmamız gerekir.raid 10 kurulu file serverimiz var hdd ışıkları bence fazla yanıyor.Teşekkürler.

Alıntı
Gönderildi : 13/08/2008 13:49
Alper OZDEMIR
(@alperozdemir)
Üye

Merhaba aşağıdaki linke göz atabilirsiniz kolay gelsin.


http://www.computerperformance.co.uk/HealthCheck/Disk_Health.htm

CevapAlıntı
Gönderildi : 13/08/2008 15:34
Rahmi DILLI
(@rahmidilli)
Tecrübeli Üye

Merhabalar,

http://www.microsoft.com/technet/archive/winntas/maintain/perform.mspx?mfr=true  

 

Disk Performance Counters

The Disk Performance counters help
you to evaluate the performance of the disk subsystem. The disk
subsystem is more than the disk itself. It will include to disk
controller card, the I/O bus of the system, and the disk. When
measuring disk performance it is usually better to have a good baseline
for performance than simply to try and evaluate the disk performance on
a case by case basis.

There are two objects for the
disk—PhysicalDisk and LogicalDisk. The counters for the two are
identical. However, in some cases they may lead to slightly different
conclusions. The PhysicalDisk object is used for the analysis of the
overall disk, despite the partitions that may be on the disk. When
evaluating overall disk performance this would be the one to select.
The LogicalDisk object analyzes information for a single partition.
Thus the values will be isolated to activity that is particularly
occurring on a single partition and not necessarily representative of
the entire load that the disk is burdened with. The LogicalDisk object
is useful primarily when looking at the affects or a particular
application, like SQL Server, on the disk performance. Again the
PhysicalDisk is primarily for looking at the performance of the entire
disk subsystem. In the list that follows, the favored object is
indicated with the counter. When the LogicalDisk and PhysicalDisk
objects are especially different, the counter will be listed twice and
the difference specifically mentioned.

PhysicalDisk : Current Disk Queue Length. This
counter provides a primary measure of disk congestion. Just as the
processor queue was an indication of waiting threads, the disk queue is
an indication of the number of transactions that are waiting to be
processed. Recall that the queue is an important measure for services
that operate on a transaction basis. Just like the line at the
supermarket, the queue will be representative of not only the number of
transactions, but also the length and frequency of each transaction.

PhysicalDisk : % Disk Time. Much
like % Processor time, this counter is a general mark of how busy the
disk is. You will see many similarities between the disk and processor
since they are both transaction-based services. This counter indicates
a disk problem, but must be observed in conjunction with the Current
Disk Queue Length counter to be truly informative. Recall also that the
disk could be a bottleneck prior to the % Disk Time reaching 100%.

PhysicalDisk : Avg. Disk Queue Length. This
counter is actually strongly related to the %Disk Time counter. This
counter converts the %Disk Time to a decimal value and displays it.
This counter will be needed in times when the disk configuration
employs multiple controllers for multiple physical disks. In these
cases, the overall performance of the disk I/O system, which consists
of two controllers, could exceed that of an individual disk. Thus, if
you were looking at the %Disk Time counter, you would only see a value
of 100%, which wouldn't represent the total potential of the entire
system, but only that it had reached the potential of a single disk on
a single controller. The real value may be 120% which the Avg. Disk
Queue Length counter would display as 1.2.

PhysicalDisk : Disk Reads/sec. This
counter is used to compare to the Memory: Page Inputs/sec counter. You
need to compare the two counters to determine how much of the Disk
Reads are actually attributed to satisfying page faults.

LogicalDisk : Disk Reads/sec. When
observing an individual application (rather a partition) this counter
will be an indication of how often the applications on the partition
are reading from the disk. This will provide you with a more exact
measure of the contribution of the various processes on the partition
that are affecting the disk.

PhysicalDisk : Disk Reads Bytes/sec. Primarily,
you'll use this counter to describe the performance of disk throughput
for the disk subsystem. Remember that you are generally measuring the
capability of the entire disk hardware subsystem to respond to requests
for information.

LogicalDisk : Disk Reads Bytes/sec. For
the partition, this will be an indication of the rate that data is
being transferred. This will be an indication of what type of activity
the partition is experiencing. A smaller value will indicate more
random reads of smaller sections.

PhysicalDisk : Avg. Disk Bytes/Read. This
counter is used primarily to let you know the average number of bytes
transferred per read of the disk system. This helps distinguish between
random reads of the disk and the more efficient sequential file reads.
A smaller value generally indicates random reads. The value for this
counter can also be an indicator of file fragmentation.

PhysicalDisk : Avg. Disk sec/Read. The
value for this counter is generally the number of seconds it takes to
do each read. On less-complex disk subsystems involving controllers
that do not have intelligent management of the I/O, this value is a
multiple of the disk's rotation per minute. This does not negate the
rule that the entire system is being observed. The rotational speed of
the hard drive will be the predominant factor in the value with the
delays imposed by the controller card and support bus system.

PhysicalDisk: Disk Reads/sec. The
value for this counter is the number of reads that the disk was able to
accomplish per second. Changes in this value indicate the amount of
random access to the disk. The disk is a mechanical device that is
capable of only so much activity. When files are closer together, the
disk is permitted to get to the files quicker than if the files are
spread throughout the disk. In addition, disk fragmentation can
contribute to an increased value here.

 

Performance Counter Instance

Guidelines for Performance Test

Guidelines for Stress Test

Database Avg. Disk sec/Read

The average value should be less than 20 ms (.20) and the maximum values should be less than 50 ms.

The maximum value should be less than 100 ms.

Log Avg. Disk sec/Write

Log disk writes are sequential, so average write latencies should be less than 10 ms, with a maximum of no more than 50 ms.

The maximum value should be no more than 100 ms.

%Processor Time

Average should be less than 80% and the maximum should be less than 90%.

Same as for Performance test.

Available Mbytes (32-bit Windows Server)

Minimum should be no less than 50 MB.

Same as for Performance test.

Free System Page Table Entries (32-bit Windows Server)

Minimum should be no less than 5000.

Same as for Performance test.

Transition Pages Repurposed/sec (Windows Server 2003)

Average should be less than 100.

Same as for Performance test.

Pages/sec (Windows 2000 Server)

Average should be less than 100.

Same as for Performance test.

Pool Nonpaged Bytes (32-bit Windows Server)

Maximum should be less than 75 MB.

Same as for Performance test.

Pool Pages Byes (32-bit Windows Server)

Maximum should be less than 180 MB.

Same as for Performance test.

Database Page Fault Stalls/sec.

Maximum should be less than 1.0.

Same as for Performance test.

 

CevapAlıntı
Gönderildi : 13/08/2008 17:34
Mesut SARIYAR
(@mesutsariyar)
Kıdemli Üye Forum Yöneticisi

Everest Ultimate.

CevapAlıntı
Gönderildi : 13/08/2008 17:34
Paylaş: