[SERVER-72033] Investigate different TicketHolder options Created: 12/Dec/22 Updated: 24/Feb/23 Resolved: 15/Dec/22 |
|
| 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: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2022-12-26 | ||||||||
| Participants: | |||||||||
| Description |
|
In effort to stabalize latency distributions and performance results, investigate different variations of the TicketHolder implementation that allow for Deprioritization |
| Comments |
| Comment by Jordi Olivares Provencio [ 15/Dec/22 ] |
|
As a result of the investigation we've chosen to go with an implementation that uses Linux's futex directly in order to avoid blocking unnecessarily. As a result, |