Re: bluestore_allocated vs bluestore_stored

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

 



Hi Maged,

min_alloc_size determines allocation granularity hence if object size isn't aligned with its value allocation overhead still takes place.

E.g. with min_alloc_size = 16K and object size = 24K total allocation (i.e. bluestore_allocated) would be 32K.

And yes, this overhead is permanent.

Thanks,

Igor

On 6/17/2019 1:06 AM, Maged Mokhtar wrote:
Hi all,

I want to understand more the difference between bluestore_allocated and bluestore_stored in the case of no compression. If i am writing fixed objects with sizes greater than min alloc size, would bluestore_allocated still be higher than bluestore_stored ? If so, is this a permanent overhead/penalty or is something the allocator can re-use/optimize later as more objects are stored ?

Appreciate any help.

Cheers /Maged

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
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]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux