From afa4a6a3118af8ed5aff38fdd077ec1090b8c008 Mon Sep 17 00:00:00 2001
From: avinassh <640792+avinassh@users.noreply.github.com>
Date: Thu, 15 Dec 2022 08:45:16 +0530
Subject: [PATCH] Update README.md

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index f19adf6..47f2bf6 100644
--- a/README.md
+++ b/README.md
@@ -90,6 +90,7 @@ I often get questions about what is next after the basic implementation. Here ar
 - Key deletion: CaskDB does not have a delete API. Read the paper and implement it
 - Instead of using a hash table, use a data structure like the red-black tree to support range scans
 - CaskDB accepts only strings as keys and values. Make it generic and take other data structures like int or bytes.
+- While startup, current implementation loads values into memory. This is unnecessary and can be avoided. Just skip the value bytes and reading just the keys enough to build KeyDir
 
 ### Level 2:
 - Hint file to improve the startup time. The paper has more details on it