From: Chris Mason <chris.mason@oracle.com>
To: Sander <sander@humilis.net>
Cc: Mike Ramsey <MikeJRamsey@comcast.net>, linux-btrfs@vger.kernel.org
Subject: Re: Phoronix article slaming BTRFS
Date: Tue, 23 Jun 2009 11:17:34 -0400 [thread overview]
Message-ID: <20090623151734.GB4379@think> (raw)
In-Reply-To: <20090623145358.GA700@cumulus>
On Tue, Jun 23, 2009 at 04:53:59PM +0200, Sander wrote:
> Chris Mason wrote (ao):
> > Jens Axboe tried to reproduce the phoronix results on his ocz drive,
> > and generally found that each run was slower than the last regardless
> > of which mount options were used. This isn't entirely surprising, but
> > it did make it very difficult to nail down good or bad performance.
>
> The performance should stabilize within a handful max fills I believe?
>
> There should be a moment where things don't get more complicated for the
> controller I thought.
That's the idea, but every device is different, and they are very
complex. Especially for write performance, tuning is a long and complex
process...a simple benchmark run where you do three tries and average
them isn't going to give you a great picture of drive performance.
-chris
next prev parent reply other threads:[~2009-06-23 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 2:51 Phoronix article slaming BTRFS Mike Ramsey
2009-06-23 10:13 ` Miguel F Mascarenhas Sousa Filipe
[not found] ` <2d23818a0906231026g6e4567fdv8eda3d6c4828ef4d@mail.gmail.com>
2009-06-23 17:28 ` Jaime sanchez
2009-06-24 1:27 ` Mike Ramsey
2009-06-24 2:20 ` Wil Reichert
2009-06-24 2:47 ` Mike Ramsey
2009-06-24 9:31 ` Bron Gondwana
2009-06-24 12:57 ` Mike Ramsey
2009-06-25 1:32 ` Bron Gondwana
2009-06-23 14:41 ` Chris Mason
2009-06-23 14:53 ` Sander
2009-06-23 15:17 ` Chris Mason [this message]
2009-06-23 16:19 ` Stephan von Krawczynski
2009-06-23 16:30 ` Chris Mason
2009-06-24 2:20 ` Mike Ramsey
2009-06-24 8:20 ` Sander
2009-06-24 8:31 ` Jens Axboe
2009-06-24 13:11 ` Mike Ramsey
2009-06-24 17:38 ` Jens Axboe
2009-06-25 8:43 ` Stephan von Krawczynski
2009-06-23 17:30 ` Jaime sanchez
2009-06-23 17:44 ` nightrow
2009-06-23 18:27 ` Jaime sanchez
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=20090623151734.GB4379@think \
--to=chris.mason@oracle.com \
--cc=MikeJRamsey@comcast.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=sander@humilis.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.