commit | 37169ec8b9476dfce6c0b8f2ffc0a69dbce73d9d | [log] [tgz] |
---|---|---|
author | vlankhaar <vlankhaar@google.com> | Mon Feb 12 17:27:06 2018 -0800 |
committer | lannadorai <lannadorai@gmail.com> | Fri Feb 23 23:43:51 2018 -0800 |
tree | aaeba606b9bd1c091e4bf63eb36469d8bd7c453f | |
parent | b5655cd0b197f5b6fe6b984186bfcf16a36d0933 [diff] |
Use unique testcase name for tests. When all tests are linked together (e.g. the 'unit_tests' build target), googletest requires that each unit test have a unique name, but sees PerfDataFiles from both perf_reader_test.cc and perf_serializer_test.cc. Using a unique (but repetitive!) testcase name is a stopgap measure until each unit test is built separately (e.g. separate bazel cc_test() targets). PiperOrigin-RevId: 185462487
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.