From: "Gérard Roudier" <groudier@free.fr>
To: Andre Hedrick <andre@linux-ide.org>
Cc: jlm <jsado@mediaone.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Poor performance during disk writes
Date: Tue, 18 Dec 2001 18:42:49 +0100 (CET) [thread overview]
Message-ID: <20011218183059.L1832-100000@gerard> (raw)
In-Reply-To: <Pine.LNX.4.10.10112181043110.21250-100000@master.linux-ide.org>
On Tue, 18 Dec 2001, Andre Hedrick wrote:
> File './Bonnie.2276', size: 1073741824, volumes: 1
> Writing with putc()... done: 72692 kB/s 83.7 %CPU
> Rewriting... done: 25355 kB/s 12.0 %CPU
> Writing intelligently...done: 103022 kB/s 40.5 %CPU
> Reading with getc()... done: 37188 kB/s 67.5 %CPU
> Reading intelligently...done: 40809 kB/s 11.4 %CPU
> Seeker 2...Seeker 1...Seeker 3...start 'em...done...done...done...
> ---Sequential Output (nosync)--- ---Sequential Input-- --Rnd Seek-
> -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --04k (03)-
> Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
> 1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809 11.4 382.1 2.4
>
> Maybe this is the kind of performance you want out your ATA subsystem.
> Maybe if I could get a patch in to the kernels we could all have stable
> and fast IO.
I rather see lots of wasting rather than performance, here. Bonnie says
that your subsystem can sustain 103 MB/s write but only 41 MB/s read. This
looks about 60% throughput wasted for read.
Note that if you intend to use it only for write-only applications,
performance are not that bad, even if just dropping the data on the floor
would give you infinite throughput without any difference in
functionnality. :-)
Gérard Roudier
Not CEO, not President of anything.
> Regards,
>
>
> Andre Hedrick
> CEO/President, LAD Storage Consulting Group
> Linux ATA Development
> Linux Disk Certification Project
next prev parent reply other threads:[~2001-12-18 19:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 0:53 jlm
2001-12-18 1:09 ` Reid Hekman
2001-12-18 2:01 ` Reid Hekman
2001-12-18 1:36 ` jlm
2001-12-18 18:46 ` Andre Hedrick
2001-12-18 17:42 ` Gérard Roudier [this message]
2001-12-18 20:34 ` Andre Hedrick
2001-12-18 19:09 ` Gérard Roudier
2001-12-19 23:26 ` jlm
2001-12-20 10:49 ` Helge Hafting
2001-12-20 11:16 ` Oops in 2.4.14-pre6 and 2.4.14-pre9aa1 Andre Margis
2001-12-21 16:29 ` Poor performance during disk writes Troy Benjegerdes
[not found] <200112201436.fBKEa2m26640@zero.tech9.net>
2001-12-20 13:27 ` Dieter Nützel
2001-12-20 14:51 ` safemode
2001-12-20 17:40 ` William Lee Irwin III
2001-12-20 18:19 ` Andrew Morton
2001-12-20 18:29 ` Dave Jones
2001-12-21 16:50 ` Jens Axboe
2001-12-21 16:50 ` Jens Axboe
[not found] ` <0112201629230E.01835@manta>
2001-12-20 19:02 ` Robert Love
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=20011218183059.L1832-100000@gerard \
--to=groudier@free.fr \
--cc=andre@linux-ide.org \
--cc=jsado@mediaone.net \
--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®