Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-96340

Remove PriorityTicketHolder

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Scheduling
    • Fully Compatible
    • Workload Scheduling 2024-11-11
    • 0

      We have been unable to enable prioritization support at the execution control layer since we added this code several years ago due to performance changes, and we don't have a clear workload that demonstrates the value to customers of doing prioritization at the execution control layer.

      We spent some time trying to resolve the performance issues by relaxing the strict queueing behavior, which helps in some workloads but hurts others, including some of the workloads we expected prioritization to show a benefit for. We also couldn't get a clear signal of user-benefit from enabling this feature as written (see SERVER-96049).

      Let's remove it for now and revisit priority support in the ticketing system when the use-case is better understood and high value and we know where in the system we want to do it. In the meanwhile, it's complicating the code by keeping everything virtualized.

            Assignee:
            drew.beckmen@mongodb.com Drew Beckmen
            Reporter:
            george.wangensteen@mongodb.com George Wangensteen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: