pEpPythonAdapter/test/profiling
Edouard Tisserant 400491f90c Updated profiling result to match latest pEpEnginge changes. Removed big intermediate measurment file 2016-12-21 15:15:50 +01:00
..
5k_pubring.gpg added heavy gpg keyring load test case, a dtrace script to trace pEpEngine and gpgme while encrypting, and a python script to analyse trace 2016-12-14 02:25:08 +01:00
README added heavy gpg keyring load test case, a dtrace script to trace pEpEngine and gpgme while encrypting, and a python script to analyse trace 2016-12-14 02:25:08 +01:00
mp_load_test.py added heavy gpg keyring load test case, a dtrace script to trace pEpEngine and gpgme while encrypting, and a python script to analyse trace 2016-12-14 02:25:08 +01:00
profile.d added heavy gpg keyring load test case, a dtrace script to trace pEpEngine and gpgme while encrypting, and a python script to analyse trace 2016-12-14 02:25:08 +01:00
results.txt Updated profiling result to match latest pEpEnginge changes. Removed big intermediate measurment file 2016-12-21 15:15:50 +01:00
trace_analysis.py Updated profiling result to match latest pEpEnginge changes. Removed big intermediate measurment file 2016-12-21 15:15:50 +01:00

README

Tool to profile pEpEngine with dtrace.

To profile :

LC_ALL=en_US.UTF-8 PYTHONPATH=`pwd`/build/lib.macosx-10.11-x86_64-3.4:`pwd`/test python3.4 mp_load_test.py wait_for_debug

wait for Alice instance to respawn after loading 5k keyring, and pass PID to dtrace script

$ sudo dtrace -s profile.d 12345 > log.dtrace

dtrace script does no processing, but just stores event, otherwise it is too slow and drops some events. Events are the analysed with a python script :

$ cat log.dtrace | python3.4 trace_analysis.py > results.txt