linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Marek Fstump <marekfstump@gmail.com>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: very poor read / write performance compared to other FS's?
Date: Fri, 13 May 2011 10:07:18 +0800	[thread overview]
Message-ID: <BANLkTi=EJP5HP9TzmpZ82evHWJR7Ygygrg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikq5eDYL0dPnB-iMPCuMfmCAqWMAw@mail.gmail.com>

On 13 May 2011 07:15, Marek Fstump <marekfstump@gmail.com> wrote:
> On Thu, May 12, 2011 at 4:39 PM, Josef Bacik <josef@redhat.com> wrote=
:
>> On Wed, May 11, 2011 at 11:33:35PM +0100, Marek Fstump wrote:
>>> Hi
>>>
>>> I am very interested in using BTRFS for my solution but in basic te=
sts
>>> it seems to be very poor on read and write performance. =A0I 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 n=
ot
>>> sure how I update BTRFS on SLES11
>>>
>>> Summary:
>>> RESULTS on link below
>>> SLES11 SP1
>>> Compared Sequential read/write performance against XFS and OCFS2
>>> Backend storage =96 FusionIO SLC SSD =3D circa 750MBsec
>>>
>>> Tests =A0set as follows:
>>> Filesystem contains 30 x 4GB files (made of random data)
>>> Read tests will read from 1 to 30 files concurrently
>>> Write tests will write 1 to 30 concurrent NEW files (simple 000=92s=
)
>>> dd -direct flag used on writes
>>>
>>> All defaults used for mounting etc.
>>>
>>> Results shown in attachment.
>>>
>>> BTRFS looks an excellent FS and perfect for my application and I am
>>> hoping that there are some factors that I am missing
>>> and would appreciate any advice / help
>>>
>>
>> Yeah our O_DIRECT performance is less than stellar, I just did a bun=
ch of work
>> to try and help us get a little better performance. =A0Would you min=
d pulling
>> down linus's git tree and testing on that and seeing if you get bett=
er
>> performance? =A0Thanks,
>>
>> Josef
>>
>
> Hi Josef
>
> Forgive me as i am a 'storage guy' - so when you say pull down linus'=
s
> git tree and test.... do you mean grab the latest kernel? =A0i know v=
ery
> stupid question, but just want to make sure i get it right... if so,
> then yes i will and i will add some more storage power also to see if
> it scales.

=46or  SLES 11, the kernel RPMs here may be your best shot:

http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_6=
4/

(eg kernel-default-2.6.38.6-1.1.x86_64.rpm)

You'll probably have to download dependent RPMs from there too.

Thanks,
  Daniel
--=20
Daniel J Blueman
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-13  2:07 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 [this message]
2011-05-12 23:34 ` Mark Fasheh

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='BANLkTi=EJP5HP9TzmpZ82evHWJR7Ygygrg@mail.gmail.com' \
    --to=daniel.blueman@gmail.com \
    --cc=josef@redhat.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).