CEPH filesystem development
 help / color / mirror / Atom feed
From: Thomas Mueller <thomas@chaschperli.ch>
To: Wido den Hollander <wido@pcextreme.nl>
Cc: ceph-devel@vger.kernel.org
Subject: Re: simple performance tests
Date: Wed, 16 Jun 2010 12:35:16 +0200	[thread overview]
Message-ID: <4C18A8E4.2070109@chaschperli.ch> (raw)
In-Reply-To: <1276681775.2492.3.camel@wido-laptop.pcextreme.nl>

On 16.06.2010 11:49, Wido den Hollander wrote:
> Hi,
>
> You were running all the Ceph components on the same host? E.g, mon, mds
> and osd on the same machine?

yes, all on one.



>
> Imho that is not the way to test Ceph.

of course this is not the inteded use uf ceph. i wanted to know the 
performance penalty between local access and access with ceph. didn't 
expect it to be that large (it's also huge with samba - so not a ceph 
specific "problem").

i'll do more testing in the next weeks in a more ceph-apropriate 
envirnoment. maybe also comparing to glusterfs.

>
> I've done some benchmarking myself with 6 physical machines for OSD's
> (different hw in each machine) and i was seeing about 30 ~ 40MB/sec over
> a Gigabit network.

what was the workload involved with your benchmarking? if these are 
large writes or reads then 30-40mb/s are IMHO not what i would expect of 
6xGigE (6x80MB/s). I would expect the GigE port of the client to be the 
bottleneck.


> Try benchmarking Ceph against NFS and you will start seeing different
> results.
>

thats why i've included samba in the mix. i wanted nfs but it crashed 
the machine (heard about nfs problems in 2.6.32). samba wins all the 
"competitions" in samba vs. ceph.

- Thomas

  reply	other threads:[~2010-06-16 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  9:15 simple performance tests Thomas Mueller
2010-06-16  9:49 ` Wido den Hollander
2010-06-16 10:35   ` Thomas Mueller [this message]
2010-06-16 14:45 ` Gregory Farnum
2010-06-17  8:53   ` Thomas Mueller
2010-06-18  8:10     ` Thomas Mueller
2010-06-16 17:58 ` K. Richard Pixley

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=4C18A8E4.2070109@chaschperli.ch \
    --to=thomas@chaschperli.ch \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wido@pcextreme.nl \
    /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