Details
-
New Feature
-
Status: Closed
-
Major - P3
-
Resolution: Won't Fix
-
None
-
None
-
None
-
Product Performance
-
Fully Compatible
Description
When profiling the performance of a given code path, certain metrics can provide valuable insight as to how the profiled code will impact system performance. An obvious example is wallclock time, but additional metrics like L2/L3/TLB cache misses, remote NUMA node memory accesses, page faults, instructions per cycle, and cycle counts can paint a more detailed picture.
The idea here is to add a simple mechanism which collects such metrics to the unit test framework.
Attachments
Issue Links
- is related to
-
SERVER-2541 Expose performance counters (Windows)
-
- Backlog
-
-
SERVER-5702 Unit test framework improvements (unittest)
-
- Closed
-