HD performances: what'd be expected?

Asked by Uqbar

Hi all.
I'm running:
Distributor ID: Ubuntu
Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy
on an "Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz" with SATA controller and disk "JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller" and "Hitachi HTS541616J9SA00" respectively. It seems it's using "*udma5".

What I'm wondering is whether the performances I have got:
 Timing cached reads: 6612 MB in 2.00 seconds = 3311.08 MB/sec
 Timing buffered disk reads: 132 MB in 3.03 seconds = 43.52 MB/sec
are similar to the ones expected to such a hardware. I see a two magnitude orders difference between "cached" and "buffered" but have no idea whether these numbers are OK or not.

Thanks in advance.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Bhavani Shankar
Solved:
Last query:
Last reply:
Revision history for this message
Uqbar (uqbar) said :
#1

Kernel is:

Linux version 2.6.24-21-generic (buildd@crested) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon Aug 25 16:57:51 UTC 2008

Revision history for this message
Best Bhavani Shankar (bhavi) said :
#2

Hello

When burning a CD or DVD, a drive doesn't write the data directly from the hard drive. Data has to be written at a constant rate, but the speed it comes from the hard drive can be variable, so the drive copies data into a buffer first. A buffer is a region of memory which can be used to temporarily hold data. A drive's buffer size (sometimes called cache size) is the amount of data it can store in preparation for writing to a disc.

and secondly

There are usually two types of disk caching:

    * Read Cache - Allows the hard disk to read data ahead in the background, so the application doesn't have to block while waiting for the data to be read, but gets the data delivered from the cache instead.
    * Write Cache - Allows the hard disk to lazy write data in the background, so the application doesn't have to block while waiting for the data to be written, but enters the cache where it is later written to the hard disk.

Disk caching greatly improves disk performance, but there is a drawback to Write caching, as anything written to the cache, which haven't been flushed to the disk will be lost when the power is lost. Most applications are aware of this behavior, and the operating system provides the ability to perform a direct write or flushed write. Write flushing means that the application will wait for the data to be written to disk before continuing, instead of just writing to the cache which completes right away.

There are three levels of disk caching:

Hard disk Cache

Disk controller Cache

Operating System Cache

So its normal and nothing is to worry

Regards

Revision history for this message
Uqbar (uqbar) said :
#3

Well, the tests I run were read test only.
Nonetheless I thank you for the support.
That solved my curiosity.

Revision history for this message
Uqbar (uqbar) said :
#4

Thanks Bhavani Shankar, that solved my question.