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 Apr 2, 2021. It is now read-only.
Description
Currently, we use a map as the main backend for database. Which requires locking on manipulating keys. Map is implemented using a linked list along with buckets. This leads to a severe issue when we want to take snapshots of data and saving them to disk.
We would have to lock the map when we wanna make a snapshot
The time to duplicate a map is also high, when we have more data we need more time to copy a snapshot. We need a highly optimized data structure which gives maximum performance and minimal locking when we wanna persist data
Steps to reproduce the behavior:
Expected behavior
Actual Behavior
OS and Other informations
Additional details
The text was updated successfully, but these errors were encountered:
Description
Currently, we use a map as the main backend for database. Which requires locking on manipulating keys. Map is implemented using a linked list along with buckets. This leads to a severe issue when we want to take snapshots of data and saving them to disk.
The time to duplicate a map is also high, when we have more data we need more time to copy a snapshot. We need a highly optimized data structure which gives maximum performance and minimal locking when we wanna persist data
Steps to reproduce the behavior:
Expected behavior
Actual Behavior
OS and Other informations
Additional details
The text was updated successfully, but these errors were encountered: