public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Pratt <slpratt@austin.ibm.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Random write regression
Date: Mon, 20 Jul 2009 08:11:42 -0500	[thread overview]
Message-ID: <4A646D0E.1060006@austin.ibm.com> (raw)

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.

Results are uploading now.  
http://btrfs.boxacle.net/repository/raid/history/History.html

These are for RAID only as single disk system still having issues 
completing btrfs runs.  Also, missing oprofile duw to oprofile causing 
an NMI and killing the system.

Chris, this was built on 7/6, but I see no new changes sine 7/2/. 

Steve



             reply	other threads:[~2009-07-20 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 13:11 Steven Pratt [this message]
2009-07-20 13:34 ` Random write regression Chris Mason
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=4A646D0E.1060006@austin.ibm.com \
    --to=slpratt@austin.ibm.com \
    --cc=linux-btrfs@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