[lkml]   [2008]   [Dec]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch] Performance Counters for Linux, v4

    I see a large (2300 instruction) fixed overhead when measuring
    retired instruction count using the "timec" command
    compared to the "pfmon" tool that comes with perfmon3
    (the pfmon tool has essentially no overhead when
    doing aggragate counts).

    Is this an inherent weakness with the new proposed performance
    counter infrastructure?

    I wanted to compare perfmon3 against Ingo's proposed
    performance counter infrastructure. This is on
    a Core2 Q6600 (the only machine I have that supports
    Ingo's codebase).

    For perfmon3 comparison, it's the same machine running patched with the appropriate full (not stripped-down)
    perfmon3 patchset available from

    All code for these tests can be had from:

    # 100 instruction test

    Testing with a 100 instruction assembly program:

    # perfmon3

    tasse:~/assembly_tests% pfmon -e INSTRUCTIONS_RETIRED ./100_insns

    # Ingo

    tasse:~/assembly_tests% ./timec -e 1 ./100_insns

    Performance counter stats for './100_insns':

    0.762 task clock ticks (millisecs)

    2446 instructions (events)

    As we can see, timec overcounts by a lot! Is it 24x, or
    a fixed value?

    # 8 billion instruction comparison

    # perfmon3

    tasse:~/assembly_tests% time pfmon -e INSTRUCTIONS_RETIRED ./8B_insns
    1.77s user 0.00s system 100% cpu 1.771 total

    Note that on almost all x86 chips that any hardware interrupt that
    occurs adds an extra retired instruction to the total count
    (some AMD engineers told me this is probably due to some artifact
    due to long pipelines and how the microcode changes user/kernel

    So you see that in 1.77s we acccumulate 1.77s*250Hz timer interrupts
    which is 442.5 which is roughly the extra instructions we see.

    (for more info on sources of non-determinism in instruction counting
    with performance counters see the paper here: )

    # ingo

    tasse:~/assembly_tests% ./timec -e 1 ./8B_insns

    Performance counter stats for './8B_insns':

    1743.446 task clock ticks (millisecs)

    8000002799 instructions (events)

    So it turns out the overhead isn't 24x, but is actually
    a fixed 2300 or so.

    Still, that's overhead perfmon does not have.

    Will this be fixed, or is it an inherent limitation of
    the new proposal?


     \ /
      Last update: 2008-12-15 18:43    [W:0.021 / U:28.200 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site