From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Sage Weil <sage@inktank.com>, "Duan, Jiangang" <jiangang.duan@intel.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: question for the new ceph-osd key/value backend
Date: Wed, 11 Dec 2013 20:12:47 +1300 [thread overview]
Message-ID: <52A8106F.30407@catalyst.net.nz> (raw)
In-Reply-To: <alpine.DEB.2.00.1312102155520.19333@cobra.newdream.net>
On 11/12/13 19:09, Sage Weil wrote:
> That is one part. The current strategy of layering on top of a file
> system and using a write-ahead journal makes sense given the existing
> linux fs building blocks, but is far from an optimal solution for many
> workloads. A k/v interface based on something leveldb probably performs
> much better for many small-object use-cases. Also, a k/v backend can take
> advatange of emerging non-block storage interfaces like NVMKV, Kinetic,
> new libraries like rocksdb, etc.
>
Yeah, the pluggable backend approach seems like a really good plan.
Regards
Mark
prev parent reply other threads:[~2013-12-11 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 2:57 question for the new ceph-osd key/value backend Duan, Jiangang
2013-12-11 6:09 ` Sage Weil
2013-12-11 6:59 ` Duan, Jiangang
2013-12-11 13:52 ` Mark Nelson
2013-12-12 1:17 ` Duan, Jiangang
2013-12-11 7:12 ` Mark Kirkwood [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=52A8106F.30407@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=jiangang.duan@intel.com \
--cc=sage@inktank.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.