commit | 733f709feefe4c3b1dc76943e4f02ee90068c86b | [log] [tgz] |
---|---|---|
author | vlankhaar <vlankhaar@users.noreply.github.com> | Tue Oct 31 16:43:19 2017 -0700 |
committer | Alexey Alexandrov <aalexand@users.noreply.github.com> | Tue Oct 31 16:43:19 2017 -0700 |
tree | c4876ff1d1228f6c9e925a125ebde68fca225c6a | |
parent | 8b0ce896364d24a920cb329f2a00dfeb9b2c2ed8 [diff] |
Copybara staging (#33) * Add dependency on googlemock to enable EXPECT_THAT(<container>, Contains(...)); This should allow simplified tests that are more readable and easier to add. (also clean up an attempt to LOG() a streamstream that failed to compile.) PiperOrigin-RevId: 174061634 * Store perf-version in profile.proto comment. PiperOrigin-RevId: 174094448
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.