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/MongoDB
MongoDBhard

Why can some MongoDB updates get slower over time (document growth/moves)?

Tags
#performance#document-growth#updates#storage-engine
Back to categoryPractice quiz

Answer

If updates make a document grow beyond its allocated space, MongoDB may need to move it to a new location, causing extra IO and fragmentation. Avoid unbounded growth, update in place when possible, and model data to keep documents stable in size.

Related questions

MongoDB
Text indexes: when would you use them and what’s a limitation?
#mongo#text-index#search
MongoDB
`$lookup`: what does it do and what is a common pitfall?
#mongo#lookup#aggregation
MongoDB
Sharded MongoDB balancing (chunk migrations): what can go wrong and how do you reduce impact?
#mongo#sharding#balancer
MongoDB
Aggregation pipeline performance: why put `$match` (and `$project`) early?
#mongo#aggregation#pipeline
MongoDB
What is a covered query in MongoDB and why can it be faster?
#mongo#indexes#covered-query
MongoDB
Sharded MongoDB: why are “scatter-gather” queries bad and how do you avoid them?
#mongo#sharding#shard-key