nxshock/zkv
1
0
Fork 0
mirror of https://github.com/nxshock/zkv.git synced 2024-11-27 11:21:02 +05:00
Code Issues Projects Releases Wiki Activity

Add info about read value issue

Browse Source
This commit is contained in:
nxshock 2022-12-10 22:00:42 +05:00
parent 28f43e56d5
commit 0458ac5152
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -10,10 +10,11 @@ Simple key-value store for single-user applications.
## Cons ## Cons
* Index stored in memory (`map[key hash (28 bytes)]file offset (int64)`) - average 200-250 Mb of RAM per 1M keys * Index stored in memory (`map[key hash (28 bytes)]file offset (int64)`)
* Need to read the whole file on store open to create file index (you can use index file options to avoid this) * Need to read the whole file on store open to create file index (you can use index file options to avoid this)
* No way to recover disk space from deleted records * No way to recover disk space from deleted records
* Write/Delete operations block Read and each other operations * Write/Delete operations block Read and each other operations
* Need to decode whole file until stored value
## Usage ## Usage
@ -96,3 +97,4 @@ Store requirements:
## TODO ## TODO
- [ ] Add recovery previous state of store file on write error - [ ] Add recovery previous state of store file on write error
- [ ] Add fast file seek to value (add compressed block start position)