Hi Victor, On 6 April 2017 at 11:43, Victor Stinner <victor.stin...@gmail.com> wrote: > Ok, let's be more concrete: I ran benchmarks with PyPy2 v5.7.1 on the > speed-python server. See attached pypy.json.gz file.
Note that unless your mails contain precise questions, you're unlikely to get much answers, because we don't know about what you need feedback. In this case, I have a strong hint about that: > If you look closer, I confirm that performance is unstable. It seems > like the distribution is multi-modal with 3 ranges around: 21.7 ms, > 27.4 ms and 33.1 ms. These numbers are too short to be precisely relevant. A major garbage collection occurs more rarely than that. So my guess is something like: you get 33ms when a major GC occurs and 21ms when it does not. Moreover, our GC is incremental, so a single major GC occurs over some non-null period of progress---possibly partly in one run and partly in the next one. (There are also minor GCs but these ones should occur every few millisecond.) A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
