From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org, Josh Durgin <josh.durgin@dreamhost.com>
Subject: Re: wip-librbd-caching
Date: Wed, 18 Apr 2012 14:50:17 +0200 [thread overview]
Message-ID: <4F8EB889.4080106@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1204121240310.21220@cobra.newdream.net>
Am 12.04.2012 21:45, schrieb Sage Weil:
> The config options you'll want to look at are client_oc_* (in case you
> didn't see that already :). "oc" is short for objectcacher, and it isn't
> only used for client (libcephfs), so it might be worth renaming these
> options before people start using them.
Hi,
I changed the values and the performance is still very good and the
memory footprint is much smaller.
OPTION(client_oc_size, OPT_INT, 1024*1024* 50) // MB * n
OPTION(client_oc_max_dirty, OPT_INT, 1024*1024* 25) // MB * n (dirty
OR tx.. bigish)
OPTION(client_oc_target_dirty, OPT_INT, 1024*1024* 8) // target dirty
(keep this smallish)
// note: the max amount of "in flight" dirty data is roughly (max - target)
But I am not quite sure about the meaning of the values.
client_oc_size Max size of the cache?
client_oc_max_dirty max dirty value before the writeback starts?
client_oc_target_dirty ???
-martin
next prev parent reply other threads:[~2012-04-18 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 19:30 wip-librbd-caching Martin Mailand
2012-04-12 19:45 ` wip-librbd-caching Sage Weil
2012-04-12 19:48 ` wip-librbd-caching Damien Churchill
2012-04-12 19:54 ` wip-librbd-caching Tommi Virtanen
2012-04-12 20:20 ` wip-librbd-caching Sage Weil
2012-04-12 19:55 ` wip-librbd-caching Greg Farnum
2012-04-18 12:50 ` Martin Mailand [this message]
2012-04-18 16:27 ` wip-librbd-caching Greg Farnum
2012-04-18 17:44 ` wip-librbd-caching Sage Weil
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=4F8EB889.4080106@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@dreamhost.com \
--cc=sage@newdream.net \
/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.