From: Jeff Wu <cpwu@tnsoft.com.cn>
To: Gregory Farnum <gregf@hq.newdream.net>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Andrew Lv <mllv@tnsoft.com.cn>
Subject: Re: Performence test on ceph v0.23 + EXT4 and Btrfs
Date: Wed, 1 Dec 2010 09:35:44 +0800 [thread overview]
Message-ID: <1291167344.1809.60.camel@cephhost> (raw)
In-Reply-To: <AANLkTinkgBwzfESaQNs0VkLn+LGbd8wEccy6LNDSFM2Z@mail.gmail.com>
在 2010-12-01三的 01:07 +0800,Gregory Farnum写道:
> On Mon, Nov 29, 2010 at 10:19 PM, Jeff Wu <cpwu@tnsoft.com.cn> wrote:
> > Is "40-50MB/s" the speed that it run bench at local btrfs disk ?
> > not the speed that run bench from client to osd server ?
> > with this speed ,run bench from client to osd server ,will which get
> > about 20~25MB/s( 40~50MB /2 )speed ?
> Data on Ceph is replicated across 2 OSDs (by default; this is
> configurable). So while figuring out potential performance involves a
> lot of variables, in a simple case like this where you aren't bounded
> by network bandwidth you'll find that your read/write performance
> simply tracks the slower disk. I'd expect your Ceph tests (at least
> the streaming ones) to run at 40-50MB/s.
Hi Greg,thank you very much for your quickly reply.
>
> Given that everything else is okay, I cannot stress enough that
> running without a journal is going to cause significant performance
> degradations. I have a hard time believing that it's responsible for
> 13-second latencies, but it's possible. So how about you set up a
> journal (it can just be a file or new partition on the drives you're
> already using) and report back your results after you do that. :)
I will add journal to ceph.conf to try it .
> Adding a journal to the OSDs lets them turn all their random writes
> into streaming ones.
> -Greg
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-01 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291001135.1872.106.camel@cephhost>
[not found] ` <1291001398.1872.107.camel@cephhost>
[not found] ` <1291001962.1872.113.camel@cephhost>
[not found] ` <1291002250.1872.116.camel@cephhost>
2010-11-29 3:53 ` Performence test on ceph v0.23 + EXT4 and Btrfs Jeff Wu
2010-11-29 17:07 ` Gregory Farnum
2010-11-30 2:55 ` Jeff Wu
2010-11-30 3:18 ` Gregory Farnum
2010-11-30 6:19 ` Jeff Wu
2010-11-30 17:07 ` Gregory Farnum
2010-12-01 1:35 ` Jeff Wu [this message]
2010-12-01 6:59 ` Jeff Wu
2010-12-01 16:05 ` Gregory Farnum
2010-12-02 1:38 ` Jeff Wu
2010-12-02 2:35 ` Gregory Farnum
2010-12-02 3:22 ` Jeff Wu
2010-12-02 6:10 ` Sage Weil
2010-12-02 7:31 ` Jeff Wu
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=1291167344.1809.60.camel@cephhost \
--to=cpwu@tnsoft.com.cn \
--cc=ceph-devel@vger.kernel.org \
--cc=gregf@hq.newdream.net \
--cc=mllv@tnsoft.com.cn \
/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