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
We currently use crossbeams SeqQueue for our DeletedEntries management (deferred dropping) which general seems like a fine choice. Unfortunately when we get to cleaning up we right now replace the entire queue and drop it, meaning we discard all blocks where as keeping the allocation for the first would be beneficial for workloads where only a small number of elements change. SeqQueue itself doesn't support that even if we did pop each element off one by one as it deallocates blocks the moment they become empty.
Might be worth exploring.
The text was updated successfully, but these errors were encountered:
We currently use crossbeams
SeqQueue
for ourDeletedEntries
management (deferred dropping) which general seems like a fine choice. Unfortunately when we get to cleaning up we right now replace the entire queue and drop it, meaning we discard all blocks where as keeping the allocation for the first would be beneficial for workloads where only a small number of elements change.SeqQueue
itself doesn't support that even if we did pop each element off one by one as it deallocates blocks the moment they become empty.Might be worth exploring.
The text was updated successfully, but these errors were encountered: