Earlier in bluestore's life, we couldn't handle a 4K min_alloc size on
NVMe without incurring pretty significant slowdowns (and also generally
higher amounts of metadata in the DB). Lately I've been seeing some
indications that we've improved the stack to the point where 4K
min_alloc no longer
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 perman
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 o
