[DOCS-14060] Investigate changes in SERVER-51285: Optimize CancelationToken-usage in TaskExecutor to avoid extra call to schedule Created: 15/Dec/20  Updated: 12/Jan/21  Resolved: 17/Dec/20

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-51285 Optimize CancelationToken-usage in Ta... Closed
Participants:
Days since reply: 3 years, 7 weeks, 6 days ago

 Description   

Description

Downstream Change Summary

Testing functionality

Description of Linked Ticket

The first implementation of SERVER-50658 leads to running callbacks on network responses being less efficient, since there are two calls to schedule the callback in the thread pool rather than one. (Once to trigger the output future, and another to run the callback.) This ticket is to optimize it to be as efficient as it was before.

SERVER-52916 also has the same issue compared to scheduleWorkAt. This ticket is to optimize all ExecutorFuture-returning functions in TaskExecutor.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Jeffrey Allen [ 17/Dec/20 ]

Closing as Won't Fix. No user-facing impact here.

Generated at Thu Feb 08 08:09:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.