From 0458ac515222c3c841b3370dff03e89565042a18 Mon Sep 17 00:00:00 2001 From: nxshock Date: Sat, 10 Dec 2022 22:00:42 +0500 Subject: [PATCH] Add info about read value issue --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cfa473f..5ed2b58 100644 --- a/README.md +++ b/README.md @@ -10,10 +10,11 @@ Simple key-value store for single-user applications. ## 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) * No way to recover disk space from deleted records * Write/Delete operations block Read and each other operations +* Need to decode whole file until stored value ## Usage @@ -96,3 +97,4 @@ Store requirements: ## TODO - [ ] Add recovery previous state of store file on write error +- [ ] Add fast file seek to value (add compressed block start position)