[SERVER-82646] Split the lock in Top class into two Created: 01/Nov/23 Updated: 24/Jan/24 Resolved: 10/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Erin McNulty |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | perf-8.0, perf-tiger, perf-tiger-handoff, perf-tiger-poc, perf-tiger-q4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2023-11-13 |
| Participants: |
| Description |
|
In the Top class, there is one lock that guards the global histogram metrics and the per collection statistics. These metrics are updated by separate methods and at different times during a query Since these two pieces of the Top class are independent, they could be guarded by two different locks instead of one lock. This will reduce cache line and atomic concurrency. |
| Comments |
| Comment by Githook User [ 10/Nov/23 ] |
|
Author: {'name': 'Erin McNulty', 'email': 'erin.mcnulty@mongodb.com', 'username': 'erin2722'}Message: |