Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14060

Investigate changes in SERVER-51285: Optimize CancelationToken-usage in TaskExecutor to avoid extra call to schedule

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      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.)

            Assignee:
            Unassigned Unassigned
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              3 years, 18 weeks, 1 day ago