All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jens Rehpöhler" <jens.rehpoehler@filoo.de>
To: Tommi Virtanen <tommi.virtanen@dreamhost.com>
Cc: Samuel Just <sam.just@dreamhost.com>, ceph-devel@vger.kernel.org
Subject: Re: ceph -w output
Date: Thu, 15 Dec 2011 10:45:15 +0100	[thread overview]
Message-ID: <4EE9C1AB.2010403@filoo.de> (raw)
In-Reply-To: <CAORUGqB4ebxyumBdAjA=HcPyPhznfaFX43seoiNQVi32Rs8onw@mail.gmail.com>

Am 14.12.2011 17:43, schrieb Tommi Virtanen:
> On Wed, Dec 14, 2011 at 00:36, Jens Rehpöhler <jens.rehpoehler@filoo.de> wrote:
>> Attached you will find the output you asked for. Is there any limitation
>> on the amount of pools ? We create
>> pools for every customer and store their VM images in that pools. So we
>> will create a lot of pools over time.
> Each pool gets its own set of PGs (Placement Groups). An OSD that
> manages too many PGs will use a lot of RAM. What is "too many" is
> debatable, and really up to benchmarks, but considering we recommend
> about 100 PGs/OSD as a starting point, you probably don't want to go
> two orders of magnitude above that.
Ok .... that will serve our needs. Remains only the "creating" question.

Any answers to that ?

Thanks a lot !

Jens

--
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

  reply	other threads:[~2011-12-15  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 19:23 ceph -w output Jens Rehpoehler
2011-12-13 17:57 ` Samuel Just
2011-12-14  8:36   ` Jens Rehpöhler
2011-12-14 16:43     ` Tommi Virtanen
2011-12-15  9:45       ` Jens Rehpöhler [this message]
2011-12-15 17:35         ` Samuel Just
2011-12-16 11:14           ` Jens Rehpöhler
2012-01-04 11:51             ` Jens Rehpöhler

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=4EE9C1AB.2010403@filoo.de \
    --to=jens.rehpoehler@filoo.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sam.just@dreamhost.com \
    --cc=tommi.virtanen@dreamhost.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.