[Speed] Testing a wide Unicode build of Python 2 on speed.python.org?

[Nick Coghlan]

On 13 April 2017 at 02:15, Victor Stinner <victor.stinner at gmail.com> wrote:
> 2017-04-12 10:52 GMT+02:00 Victor Stinner <victor.stinner at gmail.com>:
>> I'm running benchmarks with this option. Once results will be ready, I
>> will remove the old 2.7 result to replace it with the new one.
>
> Done. speed.python.org now uses UCS-4 on Python 2.7. Is it better now?

Thanks!

> Previous JSON file:
> https://github.com/haypo/performance_results/raw/master/2017-03-31-cpython/2017-04-03_16-11-2.7-23d6eb656ec2.json.gz
>
> New JSON file:
> https://github.com/haypo/performance_results/raw/master/2017-04-12-cpython/2017-04-10_17-27-2.7-e0cba5b45a5c.json.gz
>
> I see small performance differences, but they don't seem to be related
> to UTF-16 => UCS-4, but more random noise.

Given that lack of divergence and the known Unicode correctness
problems in narrow builds, I guess it doesn't make much sense to
invest time in benchmarking both of them.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia