Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-13576

Add lightweight instrumentation 'probes' for unit tests

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Performance
    • None
    • 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

          Activity

            People

              backlog-server-perf Backlog - Performance Team
              benjamin.becker Ben Becker
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: