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
{{ message }}
This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
When an entry is moved or deleted from the values file, the occupied space for the entry is just left over and not reused. We could keep a track of regions in the values file after moving or deleting entries, then reuse them when inserting/moving entries.
The data structure we use to store this information must be compact, efficient and fast (for insertion, deletion and lookups). A skip list could be a good choice, but I haven't really given a thought to this. We could also consider using a B+Tree.
The text was updated successfully, but these errors were encountered:
itsaky
changed the title
Reuse unused space in values when when values are deleted and inserted
Reuse unused space in values when values are deleted and inserted
Sep 10, 2024
itsaky
changed the title
Reuse unused space in values when values are deleted and inserted
Reuse unused space in values when values are deleted and updated out-of-place
Sep 10, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When an entry is moved or deleted from the values file, the occupied space for the entry is just left over and not reused. We could keep a track of regions in the values file after moving or deleting entries, then reuse them when inserting/moving entries.
The data structure we use to store this information must be compact, efficient and fast (for insertion, deletion and lookups). A skip list could be a good choice, but I haven't really given a thought to this. We could also consider using a B+Tree.
The text was updated successfully, but these errors were encountered: