maokaihe/mini_lsm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

i love questions

Browse Source 
Signed-off-by: Alex Chi <iskyzh@gmail.com>
This commit is contained in:
Alex Chi
2024-01-21 00:45:10 +08:00
parent 7b025687ff
commit df35a954c9
13 changed files with 80 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
mini-lsm-book/src/week2-07-snacks.md
View File

@@ -9,4 +9,11 @@ In this chapter, you will:
* Implement the batch write interface.
* Add checksums to the blocks, SST metadata, manifest, and WALs.
## Test Your Understanding
* Consider the case that an LSM storage engine only provides `write_batch` as the write interface (instead of single put + delete). Is it possible to implement it as follows: there is a single write thread with an mpsc channel receiver to get the changes, and all threads send write batches to the write thread. The write thread is the single point to write to the database. What are the pros/cons of this implementation? (Congrats if you do so you get BadgerDB!)
* Is it okay to put all block checksums altogether at the end of the SST file instead of store it along with the block? Why?
We do not provide reference answers to the questions, and feel free to discuss about them in the Discord community.
{{#include copyright.md}}