As title, new command
tests:benchmark will load a fixture into the DB (specified through command line arguments and can be your own custom file) and then benchmark either a phpunit test case or URL. The phpunit test case can be your own custom test case (so you can benchmark any bit of Piwik code). Benchmarking can be done on AWS as well as locally.
Includes some refactorings to CliMulti/RequestCommand/RunTestsOnAws/GenerateTravisYmlFile.
What is the use case? Is it to run the same piece of code several time to profile it with xhprof? Or is it to measure the execution time of a piece of code? If it's the latter, what do we compare the execute time to?
Hi @diosmosis - is it pending some work or ready to be reviewed and merged?
Thank you for this proposed pull request.
Because it was last updated more than one month ago, it is our policy to close pull requests opened for a long time without updates. If you would like to continue work on the pull request, please simply ping us to have it re-opened (after you have pushed a new commit).
We hope you understand this and we look forward to seeing an update from you on this pull request or another one!