[SERVER-70863] ServiceExecutor: makeTaskRunner instead of schedule Created: 26/Oct/22 Updated: 29/Oct/23 Resolved: 28/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Billy Donahue | Assignee: | Billy Donahue |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2022-10-31 |
| Participants: |
| Description |
|
In the ServiceExecutorSynchronous/Reserved refactor of Client code (the SessionWorkflow, really) will use a TaskRunner to schedule work, instead of calling ServiceExecutor::schedule directly. A trivial implementation of makeTaskRunner can be written for the pre-refactor case. ServiceExecutorFixed already has such an implementation in the Separating this work would enable easier performance comparisons of before and after |
| Comments |
| Comment by Githook User [ 27/Oct/22 ] |
|
Author: {'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}Message: |