Performance Impact
Parent: MongoDB Transactions · Published reference · snapshot 2026-10-15
↓ Facts as markdownall context files
Depth-first rabbithole dossier for Performance Impact; source-anchored research pack.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Facts and statements
- [low] Transactions targeting a single shard have the same performance as replica-set transactions, while those affecting multiple shards incur a greater performance cost. Sources: https://www.mongodb.com/docs/manual/core/transactions-sharded-clusters.md [source]
- [low] If an ongoing transaction holds a lock on a collection and a chunk migration involving that collection starts, the migration stages must wait for the transaction to release the locks, impacting chunk migration performance. Sources: https://www.mongodb.com/docs/manual/core/transactions-sharded-clusters.md [source]
- [low] Using multi-document transactions can improve write performance by reducing commit latency; for example, with w:majority write concern, 10 independent updates each wait for a replication round trip, whereas the same 10 updates in a transaction are replicated together at commit time, reducing latency by 10 times. Sources: https://www.mongodb.com/blog/post/performance-best-practices-transactions-and-read--write-concerns [source]
- [low] In most cases, a distributed transaction incurs a greater performance cost over single document writes, and the availability of distributed transactions should not replace effective schema design. Sources: https://www.mongodb.com/docs/manual/data-modeling/best-practices.md [source]
Related concepts
- Performance — is a part of Performance Impact
Children
- No children recorded.