File system performance, hardware performance, ext3, 3ware RAID1, etc.
Willy Tarreau <[email protected]> wrote in message
news:<[email protected]>...
Quoted 11 lines · Timothy Miller
Quoted 7 lines
For writes, iozone found an upper bound of about 10megs/sec, which is abysmal. Typically, I'd expect writes to be faster (on a single drive) than reads, because once the write is sent, you can forget about it. You don't have to wait around for something to come back, and that latency for reads can hurt performance. The OS can also buffer writes and reorder them in order to improve efficiency.
It depends on the disk too. Lots of disks (specially IDE) are far slower on writes than they are on reads.
No. Have you verified this? If you 'dd' your swap partition from /dev/zero on IDE, you'll see write performance closely matches read performance, for drives old and new.
In the case of small transfers, the drive can hand them off to the on-drive write cache (2/8MB usually). The only case where IDE disks will be 'slow' for write performance is where you have no disk I/O scheduling and lots of small reads/writes - this case wins on SCSI, but many modern IDE disks and controllers also have tagged command queuing, so it is even more of a corner case.
Dan
Signature · 4 lines
Daniel J Blueman GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...) jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++
Quoted 2 lines · Daniel Blueman
many modern IDE disks and
controllers also have tagged command queuing, so it is even more of a corner case.
Linux doesn't use tagged command queueing, though - the code has been disabled for some time. I thought the TCQ stuff was disabled because only very few disks supported it and the code wasn't reliable.
Yet you say many modern disks support it?
-- Jamie
It is a small loss that the TCQ-support implementation hasn't been stable on linux so far. I guess mostly due to the great I/O scheduling Linux has (ie anticipatory scheduler).
Yes, a growing number of IDE disk manufacturers are using native S-ATA controllers in their disks, and TCQ is one of the core features (ie unique selling point), as well as being implemented on the more lavish P-ATA controllers.
It's just a shame that there are still issues saturating a bunch of IDE disks with software RAID in the 2.6 series, but I guess that'll be ironed out in time...
Quoted 13 lines
Quoted 2 lines · Daniel Blueman
many modern IDE disks and
controllers also have tagged command queuing, so it is even more of acorner case.
Linux doesn't use tagged command queueing, though - the code has been disabled for some time. I thought the TCQ stuff was disabled because only very few disks supported it and the code wasn't reliable.
Yet you say many modern disks support it?
-- Jamie
Signature · 4 lines
Daniel J Blueman GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...) jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++
Quoted 8 lines · Daniel Blueman
It is a small loss that the TCQ-support implementation hasn't been stable on linux so far. I guess mostly due to the great I/O scheduling Linux has (ie anticipatory scheduler).
Yes, a growing number of IDE disk manufacturers are using native S-ATA controllers in their disks, and TCQ is one of the core features (ie unique selling point), as well as being implemented on the more lavish P-ATA controllers.
Ugh, you are messing PATA drive TCQ, PATA host TCQ and SATA TCQ.
Quoted 13 lines
It's just a shame that there are still issues saturating a bunch of IDE disks with software RAID in the 2.6 series, but I guess that'll be ironed out in time...
Quoted 9 lines
Quoted 2 lines · Daniel Blueman
many modern IDE disks and
controllers also have tagged command queuing, so it is even more of acorner case.
Linux doesn't use tagged command queueing, though - the code has been disabled for some time. I thought the TCQ stuff was disabled because only very few disks supported it and the code wasn't reliable.
You can re-enable it quite simply 8).
Kconfig renamed from Kconfig.orig +1 -1
@@ -441,7 +441,7 @@ # TCQ is disabled for now config BLK_DEV_IDE_TCQ bool "ATA tagged command queueing (EXPERIMENTAL)" - depends on EXPERIMENTAL && n + depends on EXPERIMENTAL help Support for tagged command queueing on ATA disk drives. This enables the IDE layer to have multiple in-flight requests on hardware that
Quoted 1 line
Quoted 1 line
Yet you say many modern disks support it?
No, only IBM/Hitachi and some WD disks support IDE TCQ.
Quoted 8 lines · Daniel Blueman
Willy Tarreau <[email protected]> wrote in message
news:<[email protected]>...Quoted 5 lines · Timothy Miller
Quoted 3 lines
For writes, iozone found an upper bound of about 10megs/sec, which is abysmal. Typically, I'd expect writes to be faster (on a single drive) than reads, because once the write is sent, you can forget about it. You don't have to wait around for something to come back, and that latency for reads can hurt performance. The OS can also buffer writes and reorder them in order to improve efficiency.
Quoted 8 lines
Quoted 2 lines
It depends on the disk too. Lots of disks (specially IDE) are far slower on writes than they are on reads.
No. Have you verified this? If you 'dd' your swap partition from
/dev/zeroon IDE, you'll see write performance closely matches read performance, for drives old and new.
And this sort of things is what I find with raw writes to the model of drive I'm using. However, it seems that there must be some issue with the 3ware 7000-2 which is killing performance, or the way the Linux kernel is dealing with this sorta-SCSI device.
The WD1200JB should get like 30-40 megs/sec, but when being accessed through the 3ware, I get 10-16 megs/sec.
What could the 3ware be doing?