[SERVER-71119] PriorityTicketHolder microbenchmarks cannot be directly compared to SemaphoreTicketHolder Created: 07/Nov/22  Updated: 29/Oct/23  Resolved: 11/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-11-14
Participants:

 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



 Comments   
Comment by Githook User [ 11/Nov/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-71119 Add PriorityTicketHolder benchmark comparable to SemaphoreTicketHolder
Branch: master
https://github.com/mongodb/mongo/commit/48dce7079ead4ec78311132a2e2224b2512ef0d3

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