From: Nat Makarevitch <nat@makarevitch.org>
To: linux-raid@vger.kernel.org
Subject: Re: RAID10 far (f2) read throughput on random and sequential / read-ahead
Date: Sun, 24 Feb 2008 00:09:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20080224T000728-690@post.gmane.org> (raw)
In-Reply-To: loom.20080222T035556-308@post.gmane.org
Nat Makarevitch <nat <at> makarevitch.org> writes:
> 'md' performs wonderfully
> random access performance remains stable and high (450
> IOPS with 48 threads, 20% writes - 10% fsync'ed), even with a fairly high
> read-ahead (16k).
Mystery solved, sorry for the noise
Explanation: I use the 'randomio' tool and searched in its sourcecode for the
various 'advise' calls (posix_fadvise(2), madvise(2)...) and forgot to check the
open call (it uses O_DIRECT!)
next prev parent reply other threads:[~2008-02-24 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 4:14 RAID10 far (f2) read throughput on random and sequential / read-ahead Nat Makarevitch
2008-02-24 0:09 ` Nat Makarevitch [this message]
2008-02-24 2:17 ` Keld Jørn Simonsen
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=loom.20080224T000728-690@post.gmane.org \
--to=nat@makarevitch.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).