From: huang jun <hjwsm1989@gmail.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: read performance not perfect
Date: Mon, 18 Jul 2011 12:51:38 +0800 [thread overview]
Message-ID: <CABAwU-YJ8DFjphavMQ+NjqPU7=fFBtwsEMzE7xT1G8gp4LywSA@mail.gmail.com> (raw)
hi,all
We test ceph's read performance last week, and find something weird
we use ceph v0.30 on linux 2.6.37
mount ceph on back-platform consist of 2 osds \1 mon \1 mds
$mount -t ceph 192.168.1.103:/ /mnt -vv
$ dd if=/dev/zero of=/mnt/test bs=4M count=200
$ cd .. && umount /mnt
$mount -t ceph 192.168.1.103:/ /mnt -vv
$dd if=test of=/dev/zero bs=4M
200+0 records in
200+0 records out
838860800 bytes (839 MB) copied, 16.2327 s, 51.7 MB/s
but if we use rados to test it
$ rados -m 192.168.1.103:6789 -p data bench 60 write
$ rados -m 192.168.1.103:6789 -p data bench 60 seq
the result is:
Total time run: 24.733935
Total reads made: 438
Read size: 4194304
Bandwidth (MB/sec): 70.834
Average Latency: 0.899429
Max latency: 1.85106
Min latency: 0.128017
this phenomenon attracts our attention, then we begin to analysis the
osd debug log.
we find that :
1) the kernel client send READ request, at first it requests 1MB, and
after that it is 512KB
2) from rados test cmd log, OSD recept the READ op with 4MB data to handle
we know the ceph developers pay their attention to read and write
performance, so i just want to confrim that
if the communication between the client and OSD spend more time than
it should be? can we request bigger size, just like default object
size 4MB, when it occurs to READ operation? or this is related to OS
management, if so, what can we do to promote the performance?
thanks very much!
next reply other threads:[~2011-07-18 4:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 4:51 huang jun [this message]
2011-07-18 17:14 ` read performance not perfect Sage Weil
2011-07-20 0:21 ` huang jun
[not found] ` <CABAwU-YKmEC=umFLzDb-ykPbzQ9s3sKoUmQbkumExrXEwyveNA@mail.gmail.com>
2011-08-04 15:51 ` Sage Weil
2011-08-04 19:36 ` Fyodor Ustinov
2011-08-04 19:53 ` Sage Weil
2011-08-04 23:38 ` Fyodor Ustinov
2011-08-05 1:26 ` Sage Weil
2011-08-05 6:34 ` Fyodor Ustinov
2011-08-05 16:07 ` Sage Weil
2011-08-05 19:30 ` Fyodor Ustinov
2011-08-05 19:35 ` Gregory Farnum
2011-08-05 20:17 ` Sage Weil
2011-08-05 21:12 ` Fyodor Ustinov
2011-08-08 17:52 ` Fyodor Ustinov
2011-08-08 19:14 ` Sage Weil
2011-08-06 11:03 ` Fyodor Ustinov
2011-08-06 19:08 ` Sage Weil
2011-08-09 3:56 ` huang jun
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='CABAwU-YJ8DFjphavMQ+NjqPU7=fFBtwsEMzE7xT1G8gp4LywSA@mail.gmail.com' \
--to=hjwsm1989@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.