From: "Dałek, Piotr" <Piotr.Dalek@ts.fujitsu.com>
To: Haomai Wang <haomaiwang@gmail.com>, Sage Weil <sweil@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: RE: [NewStore]About PGLog Workload With RocksDB
Date: Wed, 9 Sep 2015 09:28:03 +0200 [thread overview]
Message-ID: <90559C83A9C7FA45B5846C975DFA612DDB5498EAB9@ABGEX73E.FSC.NET> (raw)
In-Reply-To: <CACJqLybUOPaj3kFrn6b3-1O7fEd0zom2KR5ETC+DiPpid4HQew@mail.gmail.com>
> -----Original Message-----
> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-
> owner@vger.kernel.org] On Behalf Of Haomai Wang
> Sent: Tuesday, September 08, 2015 3:58 PM
> To: Sage Weil
> Hi Sage,
>
> I notice your post in rocksdb page about make rocksdb aware of short alive
> key/value pairs.
>
> I think it would be great if one keyvalue db impl could support different key
> types with different store behaviors. But it looks like difficult for me to add
> this feature to an existing db.
>
> [..]
Somewhat radical (and maybe also reckless) point of view here, but do we actually need that RocksDB? I'm perfectly aware of fact that writing own RocksDB replacement will take a lot of man-hours, but maybe they'll be better spent than going around current RocksDB limitations, fixing their bugs and tuning Ceph for their code?
With best regards / Pozdrawiam
Piotr Dałek
prev parent reply other threads:[~2015-09-09 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 13:58 [NewStore]About PGLog Workload With RocksDB Haomai Wang
2015-09-08 14:06 ` Haomai Wang
2015-09-08 14:12 ` Gregory Farnum
2015-09-08 14:18 ` Haomai Wang
2015-09-08 15:47 ` Gregory Farnum
2015-09-08 19:19 ` Sage Weil
2015-09-08 19:27 ` Mark Nelson
[not found] ` <55EF3639.3060108@redhat.com>
2015-09-08 19:32 ` Sage Weil
[not found] ` <6F3FA899187F0043BA1827A69DA2F7CC0361ED99@shsmsx102.ccr.corp.intel.com>
2015-09-14 12:31 ` Sage Weil
2015-09-09 7:28 ` Dałek, Piotr [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=90559C83A9C7FA45B5846C975DFA612DDB5498EAB9@ABGEX73E.FSC.NET \
--to=piotr.dalek@ts.fujitsu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=haomaiwang@gmail.com \
--cc=sweil@redhat.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.