[pypy-dev] Poor performance for Krakatau

[Maciej Fijalkowski]

you *eventually* get somewhere. Try running this:

PYPYLOG=jit-summary:- pypy <other args>

and see with what number of iterations the warmup time stops growing.
Also we have vmprof these days so maybe it's a good time to look into
the performance again, I'll keep that in mind

On Sun, Aug 9, 2015 at 5:51 AM, Robert Grosse <n210241048576 at gmail.com> wrote:
> I decided to update the benchmark today and compare it with pypy2.6. If
> anything, the performance issues with Pypy seem to have gotten worse with
> 2.6.
>
> As before, you can see the benchmark at
> https://github.com/Storyyeller/Krakatau/tree/pypy_benchmark (commit
> 234edc936b958596d843b91b963c4f61f56f2410)
>
> I also decided to compare it with different number of iterations for warmup.
>
> CPython: 12.65s
> Pypy2.6
> 100 iters: 36.83s
> 500 iters: 28.68s
> 1000 iters: 25.56s
>
> So performance does improve when increasing the amount of time spent warming
> up, but even with 1000 iterations, which is over a full minute, it is still
> half the speed of CPython.
>
>
>
>
>
>
>
>
> On Mon, Dec 8, 2014 at 7:49 AM, Armin Rigo <arigo at tunes.org> wrote:
>>
>> Hi Robert,
>>
>> On 10 November 2014 at 05:27, Maciej Fijalkowski <fijall at gmail.com> wrote:
>> > I've been looking at krakatau performance for a while, it's almost
>> > exclusively warmup time. We are going to address it, I hope rather
>> > sooner than later :-)
>>
>> We added Krakatau to the official benchmark suite.  It turns out not
>> to be exclusively warmup time: after the program is fully warmed up,
>> it is still almost 2 times slower than CPython.  We'll look at it at
>> some point now that it's on speed.pypy.org and annoying us regularly
>> :-)
>>
>>
>> A bientôt,
>>
>> Armin & Carl Friedrich
>
>