commit | 25b341a923401a468ca75d2b09f59e2532644f1c | [log] [tgz] |
---|---|---|
author | lakshmana <lakshmana@google.com> | Wed Nov 22 08:20:54 2017 -0800 |
committer | lannadorai <lannadorai@gmail.com> | Fri Dec 01 14:13:20 2017 -0800 |
tree | 25331dad2ac9649ad16dad51f58b50fd92cadd24 | |
parent | 8df65555c041f90e1a0e18f653788f7cd29bc8fd [diff] |
Add a comment to explain the usage of a 32-bit pid. PiperOrigin-RevId: 176659277
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
We appreciate your help!
Note that perf data converter and quipper projects do not use GitHub pull requests, and that we use the issue tracker for bug reports.