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 Feb 27, 2023. It is now read-only.
Currently during Update/Delete operation every write on the path from leaf to root is done in a separate call.
Those operations could be executed as batch.
Pros:
improved consistency (no orphaned nodes in case of crash)
(most probably) improved performance
Cons:
more complicated MapStore interface
Most KV stores implements batching, and actually quite often even single operation is also wrapped in a batch (AFAIK this is true for LevelDB, RocksDB, Badger).
The text was updated successfully, but these errors were encountered:
Currently during
Update
/Delete
operation every write on the path from leaf to root is done in a separate call.Those operations could be executed as batch.
Pros:
Cons:
MapStore
interfaceMost KV stores implements batching, and actually quite often even single operation is also wrapped in a batch (AFAIK this is true for LevelDB, RocksDB, Badger).
The text was updated successfully, but these errors were encountered: