Re: Questions of KeyValueStore (leveldb) backend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks!
On May 26, 2014, at 12:55 PM, Haomai Wang <haomaiwang@xxxxxxxxx> wrote:

> On Mon, May 26, 2014 at 9:46 AM, Guang Yang <yguang11@xxxxxxxxxxx> 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.
> 
>> 
>>  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).
> 
>> 
>> Thanks,
>> Guang
> 
> 
> 
> -- 
> Best Regards,
> 
> Wheat
> 

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux