[SERVER-62279] Micro-optimize the skipWriteToOrphanDocument function in case of direct writes to shards Created: 28/Dec/21 Updated: 03/Jan/22 Resolved: 03/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10 | ||||||||
| Participants: | |||||||||
| Description |
|
In the skipWriteToOrphanDocument function, in the case of direct writes to shards, it makes no sense to spend resources in extracting the collection metadata (non-negligible cost). |
| Comments |
| Comment by Antonio Fuschetto [ 03/Jan/22 ] |
|
The implementation involved in this task has been changed by |