commit | c0292875013c29e588294184e12e23168756ee93 | [log] [tgz] |
---|---|---|
author | vlankhaar <vlankhaar@google.com> | Thu Dec 07 11:12:21 2017 -0800 |
committer | lannadorai <lannadorai@gmail.com> | Tue Jan 23 10:10:12 2018 -0800 |
tree | bf5261910899aa94905d8357bc2519d76a0c310b | |
parent | b86dd5276ecdba751d56be4f1bafca7065b78ea4 [diff] |
Minor refactor/cleanups of hugepage detector and related tests Specifically - tid_match isn't important when doing address-space logic; just pid_match - address_contiguous conceptually includes pid_match, so move logic there - make simple function for setting MMapEvent filenames, deduplicating the "add new size and remove old size" logic - Simplify the test assertions to deduplicate the "has an event set" logic PiperOrigin-RevId: 178267857
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.