#273 opreport output ambiguous when event names are long

[Aaron Sawdey]

If the event names do not differ in the first 14 characters, it is unclear which columns are which counters. For instance there are a bunch of counters starting with the 15 characters PM_CMPLU_STALL_ and only differing thereafter.

CPU: ppc64 POWER8, speed 4116 MHz (estimated)
Counted PM_FUSION_TOC_GRP0_1 events (One pair of instructions fused with TOC in Group0) with a unit mask of 0x00 (No unit mask) count 10000
Counted PM_FUSION_TOC_GRP0_2 events (Two pairs of instructions fused with TOCin Group0) with a unit mask of 0x00 (No unit mask) count 10000
Counted PM_RUN_INST_CMPL events (Run_Instructions.) with a unit mask of 0x00 (No unit mask) count 100000
PM_FUSION_TOC_...|PM_FUSION_TOC_...|PM_RUN_INST_CM...|
samples| %| samples| %| samples| %|

---

21039 100.000       403 100.000   4030530 100.000 quantlib-benchmark
PM_FUSION_TOC_...|PM_FUSION_TOC_...|PM_RUN_INST_CM...|
  samples|      %|  samples|      %|  samples|      %|

[Maynard Johnson]

There's not much to be done as far as the display goes without wasting a lot of screen real estate. You'll notice that the full name of each event, along with its description, is listed in alphabetical order in the header of the report. The order of the events in the samples stats area of the report is the same order in which the events are listed in the report header. I will document this in opreport's man page.

But for ease of use, it's often a good idea for users to specify one event at a time with the opreport command; for example:
opreport event:PM_FUSION_TOC_GRP0_1 --symbols

[Aaron Sawdey]

I wouldn't mind wasting a little more screen real estate. konsole with a reasonable fontsize on a HD monitor gives over 200 columns. Why can't we add another 10 or so to each event so we can see the whole thing? Users with skinny terminals can use the event: syntax to look at just one or two.