All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: Haomai Wang <haomaiwang@gmail.com>, Guang Yang <yguang11@outlook.com>
Cc: Ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Questions of KeyValueStore (leveldb) backend
Date: Mon, 26 May 2014 11:23:00 +0200	[thread overview]
Message-ID: <538307F4.8090101@42on.com> (raw)
In-Reply-To: <CACJqLyZYe6+CBrB49B5TnyahsT6387-bWDXCQ6JCYcJGP8iyJA@mail.gmail.com>

On 05/26/2014 06:55 AM, Haomai Wang wrote:
> On Mon, May 26, 2014 at 9:46 AM, Guang Yang <yguang11@outlook.com> wrote:
>> Hello Haomai,
>> We are evaluating the key-value store backend which comes along with Firefly release (thanks for implementing it in Ceph), it is very promising for a couple of our use cases, after going through the related code change, I have a couple of questions which needs your help:
>>    1. One observation is that, for object larger than 1KB, it will be striped to multiple chunks (k-v in the leveldb table), with one strip as 1KB size. Is there any particular reason we choose 1KB as the strip size (and I didn’t find a configuration to tune this value)?
>
> 1KB is not a serious value, this value can be configured in the near future.
>

So that is currently hardcoded? I can't find any reference to it in 
config_opts.h

>>
>>    2. This is properly a leveldb question, do we expect performance degradation as the leveldb instance keeps increasing (e.g. several TB)?
>
> Ceph OSD is expected to own a physical disk, normally is several
> TB(1-4TB). LevelDB can take it easy. Especially we use it to store
> large value(compared to normal application usage).
>

With a large value you mean something like 4MB? The regular strip-size 
for RBD, CephFS and such?

>>
>> Thanks,
>> Guang
>
>
>


-- 
Wido den Hollander
42on B.V.

Phone: +31 (0)20 700 9902
Skype: contact42on
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-05-26  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  1:46 Questions of KeyValueStore (leveldb) backend Guang Yang
2014-05-26  4:55 ` Haomai Wang
2014-05-26  5:09   ` Guang Yang
2014-05-26  9:23   ` Wido den Hollander [this message]
2014-05-26  9:29     ` Haomai Wang

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=538307F4.8090101@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=haomaiwang@gmail.com \
    --cc=yguang11@outlook.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.