<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PDF export with bitmap Page background rather slow (not with lossless)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=118822#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PDF export with bitmap Page background rather slow (not with lossless)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=118822">bug 118822</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Julien Nabet from <a href="show_bug.cgi?id=118822#c4">comment #4</a>) > buovjaga: thought you might be interested in this one. > Would it be possible you give a step by step procedure to retrieve a > flamegraph? I asked the same (e-mail). Quote from Buovjaga: I started doing them after asking Noel, if he finds my callgrind traces for fileopen bugs useful. He said he always does the traces again using perf. I had forgotten that Noel wrote instructions about perf + flamegraph: <a href="https://wiki.documentfoundation.org/Development/How_to_debug#Performance_debugging_.28perf.29">https://wiki.documentfoundation.org/Development/How_to_debug#Performance_debugging_.28perf.29</a> I decided to start doing the traces with perf primarily, because callgrind can take a hell of a long time. As mentioned in the wiki section, perf "produces less detailed output than callgrind, but is much cheaper to run (since it's a sampling profiler)". If the perf result is not enough, we (or a dev wanting to fix something) could always use callgrind. Noel advised me to use a sampling frequency of 200. So if I am recording something that is not fileopen, I give the command: perf record -F 200 --call-graph dwarf --pid=`pidof soffice.bin` and then hit Ctrl-C in the terminal after the action in LibreOffice was completed. Then I do this in the same dir with the perf.data to create the flamegraph (the scripts are in my path, installed flamegraph-git from Arch Linux AUR repo): perf script | stackcollapse-perf | flamegraph --width 4096 --height 24 > perf.svg If I want to do a fileopen trace: export OOO_EXIT_POST_STARTUP=1; perf record -F 200 --call-graph dwarf ~/libreoffice/instdir/program/soffice document.odt</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>