[SERVER-73870] Investigate false sharing in PriorityTicketHolder Created: 10/Feb/23 Updated: 14/Feb/23 Resolved: 14/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Haley Connelly | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
It would be nice to evaluate if false sharing could impact performance on the PriorityTicketHolder. A starting place could be running ticketholder_bm with cache profiling. |
| Comments |
| Comment by Haley Connelly [ 10/Feb/23 ] |
|
It's possible there is no false sharing with the PriorityTicketHolder. However, it could be worthwhile to regain some performance of the switch from SempahoreTicketHolder to PriorityTicketHolder. |