Learn the vocabulary of a storage engine physically writing far more data than a logical write actually requested.
0 / 5 completed
1 / 5
At standup, a dev mentions that a storage engine ends up physically writing far more data to disk than the size of the logical write a client actually requested, because of extra work like compaction or metadata updates triggered by that write. What is this phenomenon called?
Write amplification is exactly this: a storage engine ends up physically writing far more data to disk than the size of the logical write a client requested, because that write triggers extra work like background compaction, rewriting adjacent data, or updating metadata structures. A hash collision is an unrelated hash-table concept about two keys sharing a bucket. This logical-write-triggers-extra-physical-writes phenomenon is exactly why write-heavy storage engines, especially log-structured ones, closely monitor and try to minimize their write-amplification factor.
2 / 5
During a design review, the team tunes a log-structured storage engine's compaction settings specifically to reduce how much extra physical data gets rewritten to disk for every logical write the engine accepts. Which capability does this tuning target?
Tuning compaction settings here targets reducing write amplification, since compaction is one of the main sources of extra physical rewriting triggered by logical writes, and a less aggressive or better-scheduled compaction strategy can directly cut down on how many extra bytes get rewritten to disk, and correspondingly reduce disk I/O and hardware wear, for the same amount of logical write traffic. Compaction settings having no effect at all on write amplification would contradict exactly why storage engines expose these settings for tuning in the first place. This direct link between compaction behavior and total physical writes is exactly why write amplification is a key metric operators watch.
3 / 5
In a code review, a dev notices a storage engine's default compaction strategy aggressively rewrites large amounts of adjacent data on every small logical write, with no consideration given to how much extra physical disk I/O that generates. What does this represent?
This is a missed opportunity to reduce write amplification, since an aggressive default compaction strategy that rewrites large amounts of adjacent data for every small logical write generates disproportionate extra physical disk I/O relative to the actual size of the write, when a less aggressive or better-tuned strategy could cut much of that extra rewriting. A cache eviction policy is an unrelated concept about discarded cache entries. This ignore-the-extra-I/O-cost pattern is exactly the kind of avoidable overhead a reviewer flags once write amplification is measured and found to be high.
4 / 5
An incident report shows a storage engine's disks wore out and needed replacement far sooner than expected, because its aggressive default compaction strategy rewrote large amounts of adjacent data for every small logical write, driving physical disk I/O far above what the logical write volume alone would suggest. What practice would prevent this?
Tuning the compaction strategy to reduce write amplification directly cuts down the extra physical rewriting triggered by each small logical write, which lowers total disk I/O and correspondingly extends disk lifespan, exactly addressing the premature wear described in this incident. Continuing to use the aggressive default strategy regardless of the extra I/O it generates is exactly what drove disk wear far above what the logical write volume alone would suggest. This compaction-tuning approach is the standard fix once write amplification is identified as the driver of excessive physical disk I/O in a storage engine.
5 / 5
During a PR review, a teammate asks why the team accepts some residual write amplification instead of tuning compaction all the way down to zero extra rewriting. What is the reasoning?
Compaction's extra rewriting also serves the purpose of reclaiming disk space from deleted or overwritten data and keeping the on-disk layout organized for efficient reads, so tuning it all the way down to zero extra rewriting would eliminate those benefits too, trading lower write amplification for wasted space and slower or more fragmented reads over time. This is exactly why storage engines accept some residual write amplification as the cost of keeping space reclamation and read performance healthy, tuning compaction to balance all three concerns rather than minimizing write amplification alone.
What does the "Write Amplification Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to write amplification vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.