From: Sander <sander@humilis.net>
To: Yuehai Xu <yuehaixu@gmail.com>
Cc: sander@humilis.net, linux-btrfs@vger.kernel.org, yhxu@wayne.edu,
chris.mason@oracle.com, wingedtachikoma@gmail.com
Subject: Re: BTRFS && SSD
Date: Thu, 30 Sep 2010 15:45:06 +0200 [thread overview]
Message-ID: <20100930134506.GA11295@attic.humilis.net> (raw)
In-Reply-To: <AANLkTinmBmtrv7MC=1XdN97sOFXeLvx2z=Yr+JrCzoj=@mail.gmail.com>
Yuehai Xu wrote (ao):
> On Thu, Sep 30, 2010 at 3:15 AM, Sander <sander@humilis.net> wrote:
> > Yuehai Xu wrote (ao):
> >> So, is it a bottleneck in the case of SSD since the cost for over
> >> write is very high? For every write, I think the superblocks should be
> >> overwritten, it might be much more frequent than other common blocks
> >> in SSD, even though SSD will do wear leveling inside by its FTL.
> >
> > The FTL will make sure the write cycles are evenly divided among the
> > physical blocks, regardless of how often you overwrite a single spot on
> > the fs.
> >
> >> What I current know is that for Intel x25-V SSD, the write throughput
> >> of BTRFS is almost 80% less than the one of EXT3 in the case of
> >> PostMark. This really confuses me.
> >
> > Can you show the script you use to test this, provide some info
> > regarding your setup, and show the numbers you see?
>
> My test case for PostMark is:
> set file size 9216 15360 (file size from 9216 bytes to 15360 bytes)
> set number 50000(file number is 50000)
>
> write throughput(MB/s) for different file systems in Intel SSD X25-V:
> EXT3: 28.09
> NILFS2: 10
> BTRFS: 17.35
> EXT4: 31.04
> XFS: 11.56
> REISERFS: 28.09
> EXT2: 15.94
And your testscript? You'll have to provide information on how you
create the filesystems (partitioning, etc), how you mount (options),
what versions of kernel, tools, etc, if you reboot between runs, how
many runs (also per fs), did you burn in the ssd before, modules loaded,
type and amount of hardware (controller, cpu, memory) etc, etc, etc.
Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2010-09-30 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 15:30 BTRFS && SSD Yuehai Xu
2010-09-29 17:08 ` Sean Bartell
2010-09-29 18:45 ` Yuehai Xu
2010-09-29 19:59 ` Sean Bartell
2010-09-29 21:31 ` Yuehai Xu
2010-09-30 7:15 ` Sander
2010-09-30 12:06 ` Yuehai Xu
2010-09-30 13:45 ` Sander [this message]
2010-09-30 7:51 ` David Brown
2010-09-30 12:04 ` Yuehai Xu
2010-09-29 19:39 ` Aryeh Gregor
2010-09-29 20:08 ` Sean Bartell
[not found] ` <20100929173757.7cf18c0d@simplux>
2010-09-29 18:38 ` Yuehai Xu
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=20100930134506.GA11295@attic.humilis.net \
--to=sander@humilis.net \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wingedtachikoma@gmail.com \
--cc=yhxu@wayne.edu \
--cc=yuehaixu@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).