[SERVER-52820] Reintroduce yields before waiting for data in ServiceExecutors Created: 12/Nov/20 Updated: 29/Oct/23 Resolved: 21/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Service arch 2020-11-16, Service arch 2020-11-30, Service arch 2020-12-28, Service Arch 2021-01-25 | ||||||||
| Participants: | |||||||||
| Description |
|
Previously, we yielded in the ServiceExecutorSynchronous here. This faculty needs to be introduced to other ServiceExecutors. It also can benefit from using i. using stdx::thread::hardware_concurrency() and ii. possibly scanning the processor affinities to determine if we're limited by numactl. |
| Comments |
| Comment by Githook User [ 03/Dec/20 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |