[SERVER-67542] Improve TicketHolder(s) classes Created: 27/Jun/22  Updated: 29/Oct/23  Resolved: 05/Jul/22

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

Type: Improvement Priority: Major - P3
Reporter: Haley Connelly Assignee: Jordi Olivares Provencio
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-07-11
Participants:

 Description   

Goal
Remove the assumption there should always be a reader/writer TicketHolder. Transform the FIFOTicketHolder and SemaphoreTicketHolder classes to internally manage /separate their reader/writers.

In an Ideal world, we can have a single TicketHolder instance and get rid of the TicketHolders class altogether.

Context
Right now, the TicketHolders class expects there to always be a reader and writer TicketHolder class. However, for the FIFOTicketHolder, no real performance gain is tied to separating readers / writers.

SERVER-66152 introduces the SchedulingTicketHolder with n internal Queues to keep track of.



 Comments   
Comment by Githook User [ 05/Jul/22 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-67542 Refactor TicketHolders into a composed TicketHolder
Branch: master
https://github.com/mongodb/mongo/commit/11a47eb4de1575aa06a431c0567aa6a8f35c5cf4

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