Performance Best Practices: Transactions and Read / Write Concerns | MongoDB Blog
www.mongodb.com/blog/post/performance-best-practices-transactions-and-read-write-concerns
1 Users
0 Comments
5 Highlights
0 Notes
Tags
Top Highlights
These writes cannot be flushed until transactions currently running on old snapshots commit or abort, at which time the transactions release their locks and WiredTiger can evict the snapshot.
Note that if write volumes to the server are low, you have the flexibility to tune your transactions for a longer execution time.
As a best practice, no more than 1,000 documents should be modified within a transaction.
There are no hard limits to the number of documents that can be read within a transaction.
Ready to highlight and find good content?
Glasp is a social web highlighter that people can highlight and organize quotes and thoughts from the web, and access other like-minded people’s learning.