CEPH filesystem development
 help / color / mirror / Atom feed
From: Fyodor Ustinov <ufm@ufm.su>
To: ceph-devel@vger.kernel.org
Subject: read vs write. Some tests.
Date: Wed, 01 Jun 2011 17:58:14 +0300	[thread overview]
Message-ID: <4DE65386.90209@ufm.su> (raw)


ceph - 0.28.2 from repository

client - linux 2.6.39/64

All osd servers have 4G RAM. Journal on 1G tempfs. 2*1G ethernet 
(etherchannel)

client server have 2G RAM. 2*1G ethernet (etherchannel)

In tests used "dd if=/dev/zero of=file bs=8M count=3000" for write and 
"dd if=file of=/dev/null bs=8M count=3000" for read. For rbd instead 
"file" used "/dev/rbd0".
In "ceph fs" additionaly used "iozone -a -y 8M -i 0 -i 1 -i 2 -n25g -g25g"

Tests results:

kernel ceph fs:
dd write:  149.748 s, 168 MB/s
dd read:  451.835 s, 55.7 MB/s
iozone write: 165 MB/s
iozone rewrite:  165 MB/s
iozone randow write: 165 MB/s
iozone read: 53 MB/s
iozone reread: 55 MB/s
iozone random read: 41 MB/s

rbd:
dd wite: 212.583 s, 118 MB/s
dd read: 480.374 s, 52.4 MB/s


Frankly I do not quite understand what was happening.

WBR,
     Fyodor.

                 reply	other threads:[~2011-06-01 14:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4DE65386.90209@ufm.su \
    --to=ufm@ufm.su \
    --cc=ceph-devel@vger.kernel.org \
    /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