From: David Casier AEVOO <david.casier@aevoo.fr>
To: ceph-devel@vger.kernel.org
Subject: [Documentation] Hardware recommandation : RAM and PGLog
Date: Sun, 19 Jul 2015 18:07:37 +0200 [thread overview]
Message-ID: <55ABCB49.1080304@aevoo.fr> (raw)
In-Reply-To: <55ABC8E5.1030304@aevoo.fr>
Hi,
I have a question about PGLog and RAM consumption.
In the documentation, we read "OSDs do not require as much RAM for
regular operations (e.g., 500MB of RAM per daemon instance); however,
during recovery they need significantly more RAM (e.g., ~1GB per 1TB of
storage per daemon)"
But in fact, all pg log are read in the start of ceph-osd daemon and put
in RAM ( pg->read_state(store, bl); )
Is this normal behavior or I have a defect in my environment?
Cordialement,
David Casier.
next parent reply other threads:[~2015-07-19 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55ABC8E5.1030304@aevoo.fr>
2015-07-19 16:07 ` David Casier AEVOO [this message]
2015-07-20 0:50 ` [Documentation] Hardware recommandation : RAM and PGLog huang jun
2015-07-20 13:13 ` Sage Weil
2015-07-21 15:00 ` David Casier AEVOO
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=55ABCB49.1080304@aevoo.fr \
--to=david.casier@aevoo.fr \
--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.