Mtr profiling setup

A complete generated table fixture was added. Unfortunately, imported
tables behave bad in innodb. They are subject for checksumming on and on,
so it's better to ALTER TABLE FORCE them before actually profiling.

Usage:
Put vehicle_reg.ibd in mysq-test/std_data. (cant push it; too large)
./mtr --mem main.profile
It will emit notice, that you should rerun it with --start-dirty.
Wait ~two minutes.
Check that var/mysqld.1 directory is there. If not,
it was archived by mtr. Run:
mv var/log/main.profile-innodb/mysqld.1 var

Now rerun with the dirty dir:
./mtr main.profile --start-dirty --vardir=`pwd`/var  --suite=main
You can add --gprof to collect the profiling data.
Make sure you've compiled mariadbd with -DWITH_GPROF=1.
Open gprof.msg and navigate to Call graph.
Dont use IDE to open! The file is huge. Vim/emacs is best, but maybe
sublime would work, too.

0 files changed, 0 insertions, 0 deletions