[SERVER-51285] Optimize CancelationToken-usage in TaskExecutor to avoid extra call to schedule Created: 01/Oct/20 Updated: 10/Apr/22 Resolved: 12/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Sprint: | Service Arch 2021-01-25 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Story Points: | 4 | ||||||||||||||||||||||||
| Description |
|
The first implementation of
|
| Comments |
| Comment by Matthew Saltz (Inactive) [ 12/Jan/21 ] |
|
After offline discussion, we've decided to close this ticket as "Won't fix" since it's getting too complicated. If this becomes a performance problem in the future we can fix it properly, perhaps inside futures or individual executor implementations, but not enough code currently uses this for it to cause a regression in and of itself. |