You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added a new option (see lelit/python-rapidjson@701c29f) that allows focusing on RapidJSON alone, to better coupling with the compare past runs functionality: there's an example command and its output in the README.
I will try to propose a simple command line tool that reads from one archived benchmark results (pytest-benchmark saves a JSON file under ./benchmarks at each run, when given the benchmark-autosave option: I wonder if we should make that the default, adding the option to [pytest] in setup.py...) and emits some kind of reST table to make it easier the update of ./docs/benchmarks.rst.
Activity
lelit commentedon Mar 24, 2016
I spent some time playing with pytest-benchmark, refactoring the benchmark tests over it (see lelit/python-rapidjson@cd2944c).
The new report looks like this:
I do not understand the meaning of the rightmost four columns, but it seems pretty and informative, what do you think?
lelit commentedon Mar 25, 2016
I added a new option (see lelit/python-rapidjson@701c29f) that allows focusing on RapidJSON alone, to better coupling with the compare past runs functionality: there's an example command and its output in the README.
lelit commentedon Aug 31, 2016
I will try to propose a simple command line tool that reads from one archived benchmark results (
pytest-benchmarksaves a JSON file under ./benchmarks at each run, when given thebenchmark-autosaveoption: I wonder if we should make that the default, adding the option to[pytest]in setup.py...) and emits some kind of reST table to make it easier the update of ./docs/benchmarks.rst.lelit commentedon Dec 9, 2016
This can be closed together with #42, now that #46 has been merged in.
kenrobbins commentedon Dec 9, 2016
thanks