From: Mark Nelson <mark.nelson@inktank.com>
To: Anders Saaby <anders@saaby.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: placement group sizing
Date: Fri, 26 Apr 2013 08:17:48 -0500 [thread overview]
Message-ID: <517A7E7C.8070602@inktank.com> (raw)
In-Reply-To: <02E999F2-8374-4D47-88DC-D8DC30547068@saaby.com>
On 04/25/2013 07:39 AM, Anders Saaby wrote:
> Hi,
>
> We are working on prototype infrastructure for RADOS clusters, and are now ready to deploy the first production size storage pool. One question remains; How many placement groups will we need, balancing memory footprint and ability to level data placement and data reads. - And still keeping stuff within sane limits.
>
> Our initial plan is to deploy 4PB pools, based on 4TB drives with 3 replicas (One OSD/disk). So, 3.000 disks per pool.
>
> Acording to the documentation 1), we should have: 3.000 OSDs * 100 / 3 replicas == 100.000 placement groups.
>
> From the maillist, 100.000 PG's is way more than I have seen, so, do you have any insights and advises on pg_num for a RADOS pool with these characteristics? Also, will it be a problem with a pg_num size this bit, if the pool is started out with only ~100 OSDs, and then grown to 3.000.
I pretty regularly test single-mon configurations with 64k PGs. ~100k
PGs tends to be starting to get a bit intense, but with a larger mon
cluster and some tweaking it should be doable.
I don't mean to push anything on you, but if you guys are really
thinking about deploying multiple 4PB pools, you might want to talk to
us about some kind of support/consulting agreement. That's a lot of
storage!
Mark
>
>
> Thanks in advance,
> Anders
>
> 1: http://ceph.com/docs/master/rados/operations/placement-groups/
>
> --
> 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
>
next prev parent reply other threads:[~2013-04-26 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 12:39 placement group sizing Anders Saaby
2013-04-26 12:22 ` Wido den Hollander
2013-04-26 17:07 ` Anders Saaby
2013-04-27 4:45 ` Xiaopong Tran
2013-04-29 7:17 ` Anders Saaby
2013-04-26 13:17 ` Mark Nelson [this message]
2013-04-26 17:09 ` Anders Saaby
-- strict thread matches above, loose matches on Subject: below --
2013-04-25 12:36 Anders Saaby
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=517A7E7C.8070602@inktank.com \
--to=mark.nelson@inktank.com \
--cc=anders@saaby.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.