All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: ceph-devel@vger.kernel.org
Cc: Josh Durgin <josh.durgin@dreamhost.com>
Subject: wip-librbd-caching
Date: Thu, 12 Apr 2012 21:30:16 +0200	[thread overview]
Message-ID: <4F872D48.6070801@tuxadero.com> (raw)

Hi,

today I tried the wip-librbd-caching branch. The performance improvement 
is very good particular for small writes.
I tested from within a vm with fio:

rbd_cache_enabled=1

fio -name iops -rw=write -size=10G -iodepth 1 -filename /tmp/bigfile 
-ioengine libaio -direct 1 -bs 4k

I get over 10k iops

With an iodepth 4 I get over 30k iops

In comparison with the rbd_writebackwindow I get around 5k iops with an 
iodepth of 1.

So far the whole cluster is running stable for over 12 hours.

But there is also a downside.
My typical vm are 1Gb in size, the default cache size is 200Mb, which is 
20% more memory usage. Maybe 50Mb or less will be enough?
I am going to test that.

The other point is, that the cache is not KSM enabled, therefore 
identical pages will not be merged, could that be changed, what would be 
the downside?

So maybe we could reduce the memory footprint of the cache, but keep 
it's performance.

-martin

             reply	other threads:[~2012-04-12 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 19:30 Martin Mailand [this message]
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   ` wip-librbd-caching Martin Mailand
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=4F872D48.6070801@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@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.