Re: Stat speed for objects in ceph

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

 



On 20 September 2016 at 20:30, Haomai Wang <haomai@xxxxxxxx> wrote:
> On Wed, Sep 21, 2016 at 2:26 AM, Wido den Hollander <wido@xxxxxxxx> wrote:
>>
>>> Op 20 september 2016 om 19:27 schreef Gregory Farnum <gfarnum@xxxxxxxxxx>:
>>>
>>>
>>> In librados getting a stat is basically equivalent to reading a small
>>> object; there's not an index or anything so FileStore needs to descend its
>>> folder hierarchy. If looking at metadata for all the objects in the system
>>> efficiently is important you'll want to layer an index in somewhere.
>>> -Greg
>>>
>>
>> Should we expect a improvement here with BlueStore vs FileStore? That would basically be a RocksDB lookup on the OSD, right?
>
> Yes, bluestore will be much better since it has indexed on Onode(like
> inode) in rocksdb. Although it's fast enough, it also cost some on
> construct object, if you only want to check object existence, we may
> need a more lightweight interface
>

By the way, would there be any global setting that would be capping
the overall throughput?  For instance, the current running config
shows

objecter_inflight_ops = 10240
objecter_completion_locks_per_session = 32
filestore_expected_throughput_ops = 200

I wonder what effect might happen if I increase any of these.

--
Iain Buclaw
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux