You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In segcache, the number of segments not in use is tracked by metrics: SEGMENT_FREE, which started out as the total number of segments pre-allocated. It's decremented here. If you use segment_size from the builder (defaults are here) and this metric, you can calculate how much memory is preallocated by not in use.
The question is pelikan seems preallocate a large chunk of memory, how can I make a better comparison?
I saw the crate segcache‘s code logic, to use segcache also need preallocate memory.
I'm confused, how do I compare pelikan with other hash-map solution.
The text was updated successfully, but these errors were encountered: