Message273684
| Author |
vstinner |
| Recipients |
Demur Rumed, Mark.Shannon, serhiy.storchaka, vstinner |
| Date |
2016年08月25日.22:03:17 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1472162597.8.0.16698130043.issue27213@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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. |
|