From: Mark Fasheh <mfasheh@suse.com>
To: Marek Fstump <marekfstump@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: very poor read / write performance compared to other FS's?
Date: Thu, 12 May 2011 16:34:22 -0700 [thread overview]
Message-ID: <20110512233422.GI17822@wotan.suse.de> (raw)
In-Reply-To: <BANLkTinRa9TdVOAaMt9_gcR2xDhbDWVJcA@mail.gmail.com>
On Wed, May 11, 2011 at 11:33:35PM +0100, Marek Fstump wrote:
> I am very interested in using BTRFS for my solution but in basic tests
> it seems to be very poor on read and write performance. I am
> surprised by this so suspect that maybe I am doing something
> incorrectly or that there are updates I should be using, but I am not
> sure how I update BTRFS on SLES11
Hey Marek, just fyi that the btrfs version in sles11 sp1 is old (by btrfs
standards :). That's not surprising of course as btrfs isn't supported yet
in any enterprise distributions. My guess is that you should see better
results with a more recent kernel.
--Mark
--
Mark Fasheh
prev parent reply other threads:[~2011-05-12 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 22:33 very poor read / write performance compared to other FS's? Marek Fstump
2011-05-11 22:41 ` cwillu
2011-05-26 12:57 ` Marek Fstump
2011-05-12 15:39 ` Josef Bacik
2011-05-12 23:15 ` Marek Fstump
2011-05-13 2:07 ` Daniel J Blueman
2011-05-12 23:34 ` Mark Fasheh [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=20110512233422.GI17822@wotan.suse.de \
--to=mfasheh@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marekfstump@gmail.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;
as well as URLs for NNTP newsgroup(s).