commit | 31b0c7a3a8ccb8749042a47d26582d59c9e51851 | [log] [tgz] |
---|---|---|
author | skanev <skanev@google.com> | Fri Oct 06 15:16:07 2017 -0700 |
committer | lannadorai <lannadorai@gmail.com> | Mon Oct 16 13:36:55 2017 -0700 |
tree | 46bde384cbcde917e5697247737825b2e63a5ff1 | |
parent | 35e0dde686bcee7e9c2c950884527a8ec8367015 [diff] |
Remove quadratic iteration over attrs for piped perf.data. Instead, deduplicate with a set. PiperOrigin-RevId: 171351324
The perf_to_profile
binary can be used to turn a perf.data file, which is generated by the linux profiler, perf, into a profile.proto file which can be visualized using the tool pprof.
For details on pprof, see https://github.com/google/pprof
THIS IS NOT AN OFFICIAL GOOGLE PRODUCT
To install all dependences and build the binary, run the following commands. These were tested on Debian GNU/Linux 8 (jessie):
sudo apt-get -y install autoconf automake g++ git libelf-dev libssl-dev libtool make pkg-config git clone --recursive https://github.com/google/perf_data_converter.git cd perf_data_converter make perf_to_profile
If you already have protocol buffers and googletest installed on your system, you can compile using your local packages with the following commands:
sudo apt-get -y install autoconf automake g++ git libelf-dev libssl-dev libtool make pkg-config git clone https://github.com/google/perf_data_converter.git cd perf_data_converter make perf_to_profile
Place the perf_to_profile binary in a place accessible from your path (eg /usr/local/bin).
There are a small number of tests that verify the basic functionality. To run these, after successful compilation, run:
make check
Profile a command using perf, for example:
perf record /bin/ls
The example command will generate a profile named perf.data, you should convert this into a profile.proto then visualize it using pprof:
perf_to_profile perf.data profile.pb pprof -web profile.pb
Recent versions of pprof will automatically invoke perf_to_profile
:
pprof -web perf.data