STINNER Victor added the comment: > Pybench is now only ~200ms slower instead of 1200ms slower. But the whole > point of this patch is that CALL_FUNCTION_EX shouldn't be optimized for, so > I'd much prefer real benchmarking results
FYI I released a first version of the "new" Python benchmark suite: performance 0.1 (quickly fixed with performance 0.1.1): * https://pypi.python.org/pypi/performance * https://github.com/python/benchmarks The README file contains a few information how to run a stable benchmark. Please help me to complete this documentation :-) I may help you to run these benchmarks. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue27213> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
