From: David Chinner <dgc@sgi.com>
To: "A. Liemen" <maillist@liemen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Bonnie getc reading hitting exact 65536 kb/s
Date: Mon, 17 Jul 2006 01:50:29 +1000 [thread overview]
Message-ID: <20060716155029.GR15160733@melbourne.sgi.com> (raw)
In-Reply-To: <20060715171304.59053A00A8A@smtp.funpic.de>
On Sat, Jul 15, 2006 at 07:13:10PM +0200, A. Liemen wrote:
> Hi,
>
> during some xfs tuning tests I discovered the following phenomenon.
> Maybe someone can explain it to me:
>
> Bonnie++ Reading with getc()... hits exactly an almost constant
> 65536 kbyte/s with only ~15% IO usage.
>
> iostat and bonnie output can be found under:
>
> http://alexander.liemen.net/bonnie.txt
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
storage4 40000M 64890 99 229195 39 105826 24 63895 98 350285 38 361.1 0
^^^^^^^^^ ^^^^^^^^^
It's cpu bound, not I/O bound. It can't go any faster because it's a
single threaded test....
> CPU usage is 100% (on one of the cpus) but i don't think that's the
> limiting factor since it hits that 16bit value absolut constantly.
What you are seeing is XFS issuing regular sized I/Os at a constant
throughput.
If you really think this is a 16bit ceiling, see what the block I/O tests
report in iostat - you're getting ~230MB/s for write and 350MB/s for read, so
if iostat is has a bug then you'll see it there.
> Also of interest would be why the random seeks are so bad.
Try creating more than 16 files for youre create/read/delete so
that the runtime is somewhat greater than the timer resolution....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2006-07-16 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 17:13 Bonnie getc reading hitting exact 65536 kb/s A. Liemen
2006-07-16 15:50 ` David Chinner [this message]
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=20060716155029.GR15160733@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=maillist@liemen.net \
--cc=xfs@oss.sgi.com \
/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