archive mirror
 help / color / mirror / Atom feed
From: "Oliver M. Bolzer" <>
Subject: Re: Success with  Promise FastTrak S150 TX4 (Re: [BK PATCHES] libata fixes)
Date: Mon, 10 Nov 2003 18:26:13 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Nov 10, 2003 at 11:26:16AM -0500, Jeff Garzik <> wrote...
> ># A first quick run of bonnie++ seems to show 2.6.0-test9+libata several
> ># %s slower then 2.4.22+ft3xx, but that might be related to differences
> ># between 2.4 and 2.6.
> One possibility is that queueing is not yet enabled in my sata_promise 
> driver.  Several of the SATA drivers support having multiple commands 
> outstanding per driver (tagged command queueing), but I need to do a bit 
> more work before I can enable queueing in the core.

I disabled /dev/mdX Software-RAID5 on two of the boxes that have the
hardware (got 8 of them) and did some preliminary benchmarking using
bonnie++ 1.02b. The hardware is P4-2.4GHz, 1GB RAM (highmem-enabled) wich
4 Maxtor SATA-drives with 200GBs each. The partitions I ran the tests
on are 186GB large.

2.4.22 + Promise ft3xx

Version 1.02b       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
silo4.rz.informa 2G 27330  95 62522  19 22619   6 29056  98 56311   6 159.7   0
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16  3007  98 +++++ +++ +++++ +++  3087  99 +++++ +++  9173 100

2.4.22-bk48 + 2.4.22-bk48-libata1

Version 1.02b       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
silo5.rz.informa 2G 28068  96 61698  18 23174   5 24372  77 56009   6 175.1   0
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
              files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
                 16  2986  97 +++++ +++ +++++ +++  3136  99 +++++ +++  9867  98

The performance differences are not that big that they would really
matter. One is better at one direction while the other is better at the
other direction.

I am REALLY happy that a free-as-in-freedom driver exist for the hardware
that has a much more certain future thant a
looks-like-GPL-on-the-first-look-but-one--.o-has-no-source driver. And
the libata code was really nice to read and follow, even though I knew
almost nothing about disk driver. THANK YOU!

	Oliver M. Bolzer

GPG (PGP) Fingerprint = 621B 52F6 2AC1 36DB 8761  018F 8786 87AD EF50 D1FF

  reply	other threads:[~2003-11-10 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 17:26 [BK PATCHES] libata fixes Jeff Garzik
2003-11-08 20:16 ` Sergey Vlasov
2003-11-08 20:23   ` Jeff Garzik
2003-11-10  9:52 ` Success with Promise FastTrak S150 TX4 (Re: [BK PATCHES] libata fixes) Oliver M. Bolzer
2003-11-10 16:26   ` Jeff Garzik
2003-11-10 17:26     ` Oliver M. Bolzer [this message]
2003-11-10 18:35       ` Jeff Garzik
2003-11-11  6:03         ` Kevin P. Fleming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).