commit | 68c0a772d7849c973e6994249085bbc9a1045b83 | [log] [tgz] |
---|---|---|
author | ckennelly <ckennelly@google.com> | Fri Sep 01 16:52:44 2017 +0200 |
committer | lannadorai <lannadorai@gmail.com> | Thu Sep 07 14:04:22 2017 -0700 |
tree | 71d35aa68f369f0132adef2fcac07dbf542f411f | |
parent | 3a88ebdb17b380b8452d762fce69d19cc5502ce4 [diff] |
Correct option name in perf_recorder.cc. PiperOrigin-RevId: 167274853
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