From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Random write regression
Date: Mon, 20 Jul 2009 09:34:31 -0400 [thread overview]
Message-ID: <20090720133431.GB25193@think> (raw)
In-Reply-To: <4A646D0E.1060006@austin.ibm.com>
On Mon, Jul 20, 2009 at 08:11:42AM -0500, Steven Pratt wrote:
> Finally got around to going through latest data. Seems like we lost all
> the random write performance gains. Creates are better, but total
> regression on the random workload. Sequential reads seem to have
> dropped as well.
Interesting, was this filesystem freshly created?
-chris
next prev parent reply other threads:[~2009-07-20 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 13:11 Random write regression Steven Pratt
2009-07-20 13:34 ` Chris Mason [this message]
2009-07-20 14:47 ` Steven Pratt
2009-07-21 7:04 ` Yan Zheng
2009-07-21 14:48 ` Steven Pratt
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=20090720133431.GB25193@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.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