On Mon, Oct 22, 2018 at 02:20:32PM -0700, Panos Astithas wrote: > # Import native `perf` traces > Two of the current limitations of the profiler are that it can’t profile > the very early phase of browser startup (before the profiler code has been > initialized) and that it imposes some small overhead when recording. The > overhead increases when one increases the number of sampled threads. One > nice workaround for both problems that still lets you use the profiler UI > to investigate is recording a profile on Linux with the ‘perf’ tool and > then importing the output from https://perf-html.io/. The profiler can > parse the recorded profile and display the aggregated stacks (but of course > without markers). To record a profile with the ‘perf’ command run the > following commands and then load the firefox.symbol.data output file from > https://perf-html.io: > > sudo perf record -g -F 999 -p <firefox-bin-pid> > > sudo perf script -F +pid > firefox.symbol.data
sudo shouldn't be necessary in either case. Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
