[SERVER-72396] Assess performance impact of tracking immediate priority statistics Created: 23/Dec/22  Updated: 11/Jan/23  Resolved: 11/Jan/23

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

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

Attachments: PNG File Screen Shot 2022-12-23 at 2.04.02 PM.png     PNG File Screen Shot 2022-12-23 at 2.04.14 PM.png    
Assigned Teams:
Storage Execution
Sprint: Execution Team 2023-01-23
Participants:

 Description   

Unlike the SemaphoreTicketHolder, the PriorityTicketHolder records statistics regarding immediate priority admissions. 

We should investigate whether the additional statistics tracking has an impact on performkance



 Comments   
Comment by Jordi Olivares Provencio [ 11/Jan/23 ]

louis.williams@mongodb.com haley.connelly@mongodb.com After looking at the performance with and without recording statistics my assessment is that we shouldn't record immediate priority statistics. Not doing so introduces some regressions that are undesired.

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