Re: hybrid allocator based on btree allocator

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

 



Hi  Kefu and Adam,

curious whether we have reliable enough set of numbers on how spatially efficient btree allocator is? I recall some Adam's comment in the PR showing 2x saving in BTree allocator vs. AVL on.

But the data set there seems to be relatively small - total consumed RAM is just a few MBs. Anything else available?

I recall Adam promised to run more vast testing at perf meeting....


Thanks,

Igor



On 6/25/2021 11:35 AM, Kefu Chai wrote:
hi Adam,

while looking at Hybrid Allocator [0] and the newly introduced Btree
Allocator [1], i am wondering if we still need the bitmap allocator to
cap the memory usage due to the large overhead of AVL allocator?
because btree is much more spatially efficient than AVL tree.

cheers

---
[0] https://github.com/ceph/ceph/pull/33365
[1] https://github.com/ceph/ceph/pull/41828
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx

_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx




[Index of Archives]     [CEPH Users]     [Ceph Devel]     [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