mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin A. Fink" <fink@mpe.mpg.de>
To: linux-kernel@vger.kernel.org
Subject: SATA-performance part 2
Date: Wed, 14 Feb 2007 10:11:20 +0100	[thread overview]
Message-ID: <200702141011.20832.fink@mpe.mpg.de> (raw)

Dear all,

now I installed oprofile as suggested, and very interesting things happend:

System: OpenSuSE 10.2 with AHCI on, disk: Solid State Disk (Flash Disk)
Test: Write blocks of 1MB. Do fsync() every 1GB. Measure time for each GB.

before installation of oprofile:
test						OpenSuSE 10.2			FreeBSD 6.2
write to raw device  25GB		26+/-1 MB/s at 4-10% CPU	48+/-0 MB/s at 1% CPU
write to ext3 2GB			39+/-5 MB/s at 10-15% CPU

after installation of oprofile:
test						OpenSuSE 10.2			FreeBSD 6.2
write to raw device  25GB		48+/-0.5 MB/s at 4-10% CPU	49+/-0 MB/s at 1% CPU
write to ext3 (writeback) 2GB	40+/-5 MB/s at 10-15% CPU

after deinstallation of oprofile and only soft reboots (no hardware power off) 
these values STAYED (linux 48 MB/s) !! even for a brand new installation of 
OpenSuSE 10.2 to another partition!
After a hardware power off everything was again like before (26 MB/s).

So now the interesting questions to me are:

1. What is oprofile doing with my system ?? Especially what is been changed 
that remains a reboot ??

2. Buffers: All those that told me, that linux raw devices are totally 
unbuffered and thus are slower than devices with filesystems. Are you sure? 
If yes, where do you think comes this increase of speed (26 to 48) ??

3. Advices using ext3 with writeback option: I do not see an increase of 
performance with that.

Thanks,

Martin

             reply	other threads:[~2007-02-14  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  9:11 Martin A. Fink [this message]
2007-02-14 17:25 ` Arjan van de Ven

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=200702141011.20832.fink@mpe.mpg.de \
    --to=fink@mpe.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

all inboxes | Powered by JetHome®