| commit | 2b536c9735b5e142608c7d3976dd2808a80a05cb | [log] [tgz] |
|---|---|---|
| author | lannadorai <lannadorai@gmail.com> | Tue Jul 11 18:10:46 2017 -0700 |
| committer | Alexey Alexandrov <aalexand@users.noreply.github.com> | Tue Jul 11 18:10:46 2017 -0700 |
| tree | 01bd5413f3431879db441c921748739e1e1fff2e | |
| parent | 48a540dd9376e37bb5edcc89ddd0715dcd867145 [diff] |
Project import generated by Copybara. (#13) PiperOrigin-RevId: 160971937
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