pitfall on merge iterator

Signed-off-by: Alex Chi <iskyzh@gmail.com>
This commit is contained in:
Alex Chi
2024-01-21 12:03:40 +08:00
parent 892e6ab8f7
commit c6e700e2ea
3 changed files with 15 additions and 1 deletions

View File

@@ -9,7 +9,8 @@ In this chapter, you will:
## Test Your Understanding
* (I know this is stupid but) could you please repeat the definition of read/write/space amplifications? What are the ways to accurately compute them, and what are the ways to estimate them?
* (I know this is stupid but) could you please repeat the definition of read/write/space amplifications?
* What are the ways to accurately compute the read/write/space amplifications, and what are the ways to estimate them?
* Is it correct that a key will only be purged from the LSM tree if the user requests to delete it and it has been compacted in the bottom-most level?
* Is it a good strategy to periodically do a full compaction on the LSM tree? Why or why not?
* Actively choosing some old files/levels to compact even if they do not violate the level amplifier would be a good choice, is it true? (Look at the Lethe paper!)