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

PriorityTicketHolder microbenchmarks cannot be directly compared to SemaphoreTicketHolder

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-11-14

    Description

      The PriorityTicketHolder will not have comparable performance to the SemaphoreTicketHolder when the priority of operations are varied. This is because low priority operations will always wait for the normal priority queue to be cleared in the contended case. 

      Since microbenchmarks are relatively cheap, one option is to have two variations of the PriorityTicketHolder benchruns:
      (1) Where all operations are normal - this allows for a more reasonable direct comparison to SemaphoreTicketHolder performance since the SemaphoreTicketHolder disregards ticket priority
      (2) Where operations are varied low and high - this will allow for iterative comparisons of the PriorityTicketHolder's performance when it manages a balanced load of low and high priority operations

      Attachments

        Activity

          People

            haley.connelly@mongodb.com Haley Connelly
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: