Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Databases
Databaseshard

What is write amplification and why do many indexes make writes slower?

Tags
#performance#indexes#write-amplification#trade-offs
Back to categoryPractice quiz

Answer

Write amplification means one logical write causes multiple physical writes: the table row plus every affected index (and often WAL/redo logs). More indexes usually speed up reads but make inserts/updates/deletes slower and increase storage and maintenance cost.

Related questions

Databases
Denormalization: when might you do it and what’s the trade‑off?
#database#denormalization#performance
Databases
What is a covering index (index‑only scan) and why can it be faster?
#database#indexes#covering-index
Databases
Composite index order: why does column order matter?
#database#indexes#composite-index
Databases
Foreign keys: why use them and what’s a trade‑off?
#database#foreign-key#integrity
Databases
Why can `LIKE '%term%'` be slow and what are common alternatives?
#sql#like#indexes
Databases
Why can the optimizer choose a bad query plan and how do statistics help?
#optimizer#statistics#cardinality