[SERVER-81155] Use move semantic to avoid copying all chunks in createCollection coordinator Created: 18/Sep/23 Updated: 29/Oct/23 Resolved: 20/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.24, 7.0.1, 4.4.24, 6.0.10, 5.0.21, 7.1.0-rc3 |
| Fix Version/s: | 7.2.0-rc0, 5.0.22, 6.0.11, 7.0.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | car-71-backport-declined | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding EMEA
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v7.1, v7.0, v6.0, v5.0, v4.4
|
||||
| Sprint: | Sharding EMEA 2023-10-02 | ||||
| Participants: | |||||
| Description |
|
In the createCollection coordinator we accidentally copy all chunks after we serialize them. To avoid this copy we could simply use move semantic. While in versions 6.0+ this is not particularly problematic because we usually do not have a huge number of chunks, in previous versions (<= 5.0) the number of chunks could be very high, on the order of millions. |
| Comments |
| Comment by Githook User [ 21/Sep/23 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |
| Comment by Githook User [ 21/Sep/23 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |
| Comment by Githook User [ 21/Sep/23 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |
| Comment by Githook User [ 20/Sep/23 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |