From: "Grant Grundler" <grundler@google.com>
To: kenneth johansson <ken@kenjo.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: weird throughput on write to SATA disk
Date: Mon, 13 Oct 2008 18:33:55 -0700 [thread overview]
Message-ID: <da824cf30810131833g6e509d0dvb6cce6c7220a1a28@mail.gmail.com> (raw)
In-Reply-To: <1223936351.3947.41.camel@duo>
On Mon, Oct 13, 2008 at 3:19 PM, kenneth johansson <ken@kenjo.org> wrote:
...
>> Can you try "dd oflag=direct if=/dev/null of=/dev/sdb bs=64k"?
>
> I changed to use O_DIRECT and it's much more consistent now. 69-75 with
> 74 about 95% of the time.
That's low but it could be worse. Many things can contribute to slow
disks. Favorites are overtemp (See SMART field 194) and vibration (no
measurement possible w/o special equipment). "dd" isn't exactly a
performance application until one uses really big block sizes (1MB or
larger). sgp_dd is better since it is multi-threaded. fio has all the
right knobs to test disk perf and measure it properly.
> the disk is supposed to have 105 115 sustained
> data rate.
Where did 105-115 number come from?
The best I've seen to date with 7200 rpm drives was 108MB/s on the
outside diameter. That degrades slowly until about 60-70% towards the
inside diameter and then drops off dramatically (down to something
like 50MB/s).
hth,
grant
next prev parent reply other threads:[~2008-10-14 1:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 19:19 weird throughput on write to SATA disk kenneth johansson
2008-10-13 21:07 ` Grant Grundler
2008-10-13 21:22 ` kenneth johansson
2008-10-13 21:34 ` Grant Grundler
2008-10-13 21:35 ` Grant Grundler
2008-10-13 22:19 ` kenneth johansson
2008-10-14 1:33 ` Grant Grundler [this message]
2008-10-14 9:14 ` kenneth johansson
2008-10-14 9:17 ` Tejun Heo
2008-10-14 19:10 ` kenneth johansson
2008-10-14 16:09 ` Grant Grundler
2008-10-13 22:39 ` Alan Cox
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=da824cf30810131833g6e509d0dvb6cce6c7220a1a28@mail.gmail.com \
--to=grundler@google.com \
--cc=ken@kenjo.org \
--cc=linux-ide@vger.kernel.org \
--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