[SERVER-37229] Switch to unordered write ops in $out Created: 20/Sep/18  Updated: 29/Oct/23  Resolved: 12/Oct/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Performance
Affects Version/s: None
Fix Version/s: 4.1.5

Type: Improvement Priority: Major - P3
Reporter: Charlie Swanson Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Query 2018-10-22
Participants:

 Description   

We want to avoid making guarantees to the client about which order the updates/inserts are applied in, and how one error impacts which other updates may succeed. Moving to unordered operations should allow for a performance gain in sharded output collections, since we will be able to send large batches instead of repeatedly having to wait for responses before continuing.



 Comments   
Comment by Githook User [ 23/Oct/18 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-37229 Remove commented-out code
Branch: master
https://github.com/mongodb/mongo/commit/860c81bdadfbbd9ed64d42e8ec1ebb5589d9a935

Comment by Githook User [ 12/Oct/18 ]

Author:

{'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}

Message: SERVER-37229: Switch to unordered write ops ini $out
Branch: master
https://github.com/mongodb/mongo/commit/267bbff2d931ab1ddabfbab18da96d018422f7fd

Generated at Thu Feb 08 04:45:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.