[Bug gprofng/30898] New: consider multi-threading for gprofng display text

[bugmenot at mailinator dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30898

            Bug ID: 30898
           Summary: consider multi-threading for gprofng display text
           Product: binutils
           Version: 2.41
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: gprofng
          Assignee: vladimir.mezentsev at oracle dot com
          Reporter: bugmenot at mailinator dot com
  Target Milestone: ---

recording a sample program that uses lots of shared object files (most loaded
with dlopen) using "gprofng collect app" is quite fast; doing the "gprofng
display html" afterwards was... unexpected.


The first process took several minutes and wrote hundreds of MBs (mostly
disassembly) to disk
/tmp/install/bin/gp-display-text -limit 1000000 -viewmode machine -compare off
-script display.2.html/gp-script /tmp/binutils-2.41/build/test.2.er

The second process ran even much longer (actually I've killt it after taking a
single complete core for over 2 hours)

perl /tmp/install/bin/gp-display-html --whoami=gprofng display html test.2.er


Both processes ran on a single core, so the main question here is: is it
possible to use multiple cores for those tasks?


Also running 
"gprofng display text -metrics name:soname:e.%totalcpu -disasm func1" (this
function showed 5% usage in the "-functions" flavor) took 6 minutes (that's a
huge, generated function).



Can anything be done about the run time for the "gprofng display" command?


Maybe the default for "gprofng display html" should be to NOT include
disassembly (this may be a separate issue though)?

-- 
You are receiving this mail because:
You are on the CC list for the bug.