From: Mark Nelson <mark.nelson@inktank.com>
To: Aleksey Samarin <nrg3tik@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: poor performance
Date: Sun, 04 Nov 2012 06:29:28 -0600 [thread overview]
Message-ID: <50965FA8.7040501@inktank.com> (raw)
In-Reply-To: <CAFjNkqRPC7MDm86LBYCD+reXePNjWzZBPz7yPn9pv553TYHPjA@mail.gmail.com>
On 11/04/2012 03:58 AM, Aleksey Samarin wrote:
> Hi all
>
> Im planning use ceph for cloud storage.
> My test setup is 2 servers connected via infiniband 40Gb, 6x2Tb disks per node.
> Centos 6.2
> Ceph 0.52 from http://ceph.com/rpms/el6/x86_64
> This is my config http://pastebin.com/Pzxafnsm
One thing that may be problematic is that I don't think centos 6.2 has a
new enough version of glibc to support syncfs (Assuming it's even
backported in their kernel). You may want to try moving the mons off to
another node, and reducing each node down to a single OSD/disk and test
it out to see what happens. Also, we are starting to ship some tools
Sam wrote to test underlying filestore performance. I think Gary has
been working on getting some of those tools packaged up.
> journal on tmpfs
> well, im create bench pool and test it:
> ceph osd pool create bench
> rados -p bench bench 30 write
>
> Total time run: 43.258228
> Total writes made: 151
> Write size: 4194304
> Bandwidth (MB/sec): 13.963
> Stddev Bandwidth: 26.307
> Max bandwidth (MB/sec): 128
> Min bandwidth (MB/sec): 0
> Average Latency: 4.48605
> Stddev Latency: 8.17709
> Max latency: 29.7957
> Min latency: 0.039435
>
> when i do rados -p bench bench 30 seq
> Total time run: 20.626935
> Total reads made: 275
> Read size: 4194304
> Bandwidth (MB/sec): 53.328
> Average Latency: 1.19754
> Max latency: 7.0215
> Min latency: 0.011647
>
> I tested the single drive via dd if=/dev/zero of=/mnt/hdd2/testfile
> bs=1024k count=20000
> result: 158 MB/sec
>
> Anyone can tell me why such a weak performance? Maybe I missed something?
>
> All the best, Alex!
> --
> 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
>
prev parent reply other threads:[~2012-11-04 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 9:58 poor performance Aleksey Samarin
2012-11-04 11:00 ` Gregory Farnum
2012-11-04 12:04 ` Aleksey Samarin
2012-11-04 12:15 ` Gregory Farnum
2012-11-04 12:18 ` Gregory Farnum
2012-11-04 12:26 ` Aleksey Samarin
2012-11-04 12:39 ` Gregory Farnum
2012-11-04 12:52 ` Aleksey Samarin
2012-11-04 13:18 ` Aleksey Samarin
2012-11-04 13:52 ` Mark Nelson
2012-11-04 15:13 ` Aleksey Samarin
2012-11-15 21:16 ` Gregory Farnum
2012-11-16 7:41 ` Aleksey Samarin
2012-11-04 12:29 ` Mark Nelson [this message]
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=50965FA8.7040501@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=nrg3tik@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 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.