Currently, we are seeing a case where the ticketholder_bm benchmark performance of the PriorityTicketHolder degrades significantly on outlier runs. In general, the PriorityTicketHolder microbenchmarks perform comparable to that of the SemaphoreTicketHolder, consistently surpassing the SemaphoreTicketHolder performance with benchmark runs of 1024 threads.

After performing some analysis, we discovered that outlier runs with poor performance were spending a significant amount of time (~29% compared to ~2% in standard runs) in _pthread_rwlock_rdlock. 

We suspect this could be due to the use of the shared_mutex, and sub-optimal waits for shared readers.