From: Mike <mike.almateia@gmail.com>
To: Wido den Hollander <wido@42on.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: BlueStore and maximum number of objects per PG
Date: Wed, 22 Feb 2017 17:34:22 +0300 [thread overview]
Message-ID: <1487774062.1919.1.camel@gmail.com> (raw)
In-Reply-To: <1002796178.10638.1487707472256@ox.pcextreme.nl>
On Tue, 2017-02-21 at 21:04 +0100, Wido den Hollander wrote:
> Hi,
>
> I'm about to start a test where I'll be putting a lot of objects into BlueStore and
> see how it holds.
>
> The reasoning behind is that I have a customer which has 165M objects in it's cluster
> which results in some PGs having 900k objects.
>
> For FileStore with XFS this is quite heavy. A simple scrub takes ages.
>
> The problem is that we can't simply increase the number of PGs since that will
> overload the OSDs as well.
Also the problem stands if have a huge amount _small_ objects: capacity of hardware is
enough (20% used) but PG quantity isn't.
>
> On the other hand we could add hardware, but that also takes time.
>
> So just for the sake of testing I'm looking at trying to replicate this situation
> using BlueStore from master.
>
> Is there anything I should take into account? I'll probably be just creating a lot
> (millions) of 100 byte objects in the cluster with just a few PGs.
>
> Wido
> --
> 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:[~2017-02-22 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 20:04 BlueStore and maximum number of objects per PG Wido den Hollander
2017-02-22 2:53 ` Mark Nelson
2017-02-22 10:51 ` Wido den Hollander
2017-03-09 13:38 ` Wido den Hollander
2017-03-09 14:10 ` Mark Nelson
2017-03-10 10:23 ` Wido den Hollander
2017-02-22 14:34 ` Mike [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=1487774062.1919.1.camel@gmail.com \
--to=mike.almateia@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@42on.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.