[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: |
| Comment by Githook User [ 12/Oct/18 ] |
|
Author: {'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}Message: |