On 12 February 2016 at 08:50, Yury Selivanov <yselivanov...@gmail.com> wrote:
> On 2016-02-11 5:37 PM, Victor Stinner wrote:
>> 2016-02-11 19:36 GMT+01:00 Brett Cannon <br...@python.org>:
>>> Are we happy with the current benchmarks?
>>
>> bm_regex8 looks unstable, but I don't know if it's an issue of the
>> benchmark itself or perf.py (see the other thread "[Speed] Any changes
>> we want to make to perf.py?").
>
> It's super unstable. As well as telco -- I don't trust those benchmarks.
telco covers a fairly important use case in the form of "Do things
that billing applications need to do". Spending a few months running
and re-running that to help optimise the original Python
implementation of decimal was one of my first contributions to CPython
(including figuring out the "int("".join(map(str, digits)))" hack that
proved to be the fastest way in CPython to convert a tuple of digits
into a Python integer, much to the annoyance of the PyPy folks trying
to accelerate that code later).
It's probably best to consider telco as a microbenchmark of decimal
module performance rather than as a general macrobenchmark, though -
that's why the integration of cdecimal improved it so dramatically.
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
_______________________________________________
Speed mailing list
Speed@python.org
https://mail.python.org/mailman/listinfo/speed
