-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Workload Scheduling
-
ALL
-
WS Prioritized List
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
After spending a decent amount of time looking at a customer issue on 6.0 with heavy TCMalloc spinlock contention, I had them run on 8.0, but the spinlock metric was missing, so I could not determine whether the new allocator was any better.
That metric was incredibly valuable for quickly identifying allocator contention, and I think we need to find a suitable replacement for 8.0.
In particular, we need a metric that tells us how many operations are bottlenecked on the allocator.
- is related to
-
SERVER-87145 Investigate hooking into spinlock for delay statistics in new tcmalloc
-
- Closed
-