From: Mark Nelson <mark.nelson@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Alexandre DERUMIER <aderumier@odiso.com>, ceph-devel@vger.kernel.org
Subject: Re: Heavy speed difference between rbd and custom pool
Date: Tue, 19 Jun 2012 08:01:30 -0500 [thread overview]
Message-ID: <4FE0782A.1060104@inktank.com> (raw)
In-Reply-To: <4FE01CE7.8000204@profihost.ag>
On 06/19/2012 01:32 AM, Stefan Priebe - Profihost AG wrote:
> Am 19.06.2012 06:41, schrieb Alexandre DERUMIER:
>> Hi Stephann
>> recommandations are 30-50 PGS by osd if I remember.
>>
> rbd, data and metadata have 2176 PGs with 12 OSD. This is 181,333333333
> per OSD?!
>
> Stefan
That's probably fine, it just means that you will have a better
pseudo-random distribution of OSD combinations (It does have higher
cpu/memory overhead though). Figuring out how many PGs you should have
per OSD depends on a lot of factors including how many OSDs you have,
how many nodes, CPU, memory, etc. I'm guessing ~180 per OSD won't cause
problems. On the other hand, with low OSD counts you could probably
have fewer and be fine too.
Mark
next prev parent reply other threads:[~2012-06-19 13:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 21:39 Heavy speed difference between rbd and custom pool Stefan Priebe
2012-06-18 22:23 ` Mark Nelson
2012-06-18 22:41 ` Dan Mick
2012-06-19 6:06 ` Stefan Priebe
2012-06-19 6:30 ` Stefan Priebe - Profihost AG
2012-06-19 4:41 ` Alexandre DERUMIER
2012-06-19 6:32 ` Stefan Priebe - Profihost AG
2012-06-19 13:01 ` Mark Nelson [this message]
2012-06-19 13:14 ` Stefan Priebe - Profihost AG
2012-06-19 14:05 ` bad performance fio random write - rados bench random write to compare? Alexandre DERUMIER
2012-07-02 19:52 ` Gregory Farnum
2012-07-03 7:31 ` Stefan Priebe - Profihost AG
2012-06-19 15:42 ` Heavy speed difference between rbd and custom pool Sage Weil
2012-06-19 16:24 ` Stefan Priebe
2012-06-19 16:27 ` Sage Weil
2012-06-19 16:29 ` Dan Mick
2012-06-20 6:46 ` Stefan Priebe - Profihost AG
2012-06-20 23:21 ` Dan Mick
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=4FE0782A.1060104@inktank.com \
--to=mark.nelson@inktank.com \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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