In a previous post, I talked about the method Skoll used to collect MySQL runtime information for non-default configurations. At the time, the runtime information was collected after all of the MySQL tests were executed, which means the runtime information was accumulated from all tests run. There was no way to decipher how each test contributed to this accumulated runtime information. A greater degree of granularity can provide better understanding of the MySQL runtime behavior.
To collect runtime information for each MySQL test, the Skoll client still compiles MySQL as described in the previous post. Instead of running the "mysql-test-run" script with no arguments (which runs all available tests in the source tree), Skoll client calls "mysql-test-run [TESTCASE]" to run one specific test. …
[Read more]