Hello Sébastien,
thank you for sharing these numbers. I'm glad to see that my checkin worked so
well :-)
Indeed, CPython is still quite faster: it might be the case that ~1.5 seconds
is still not enough for the jit to fully warm up (especially if there are a
lot of hot branches), or simply that you are encountering another case in
which we do bad.
I don't think I'll have time to investigate further in the next few days,
though, but I might do it next week.
ciao,
Anto
On 02/21/2012 07:03 PM, Sébastien Volle wrote:
Hello,
I ran stock pypy 1.8 and latest version of ctypes from mercurial and here are
the results with a capture file with around 110,000 ARP packets:
Stock pypy 1.8:
-----------------------------------------------
elapsed time : 2419.07ms
Total packets : 110450
packets/s : 45658.02
pypy 1.8 binary and latest ctypes:
-----------------------------------------------
elapsed time : 1410.92ms
Total packets : 110450
packets/s : 78282.04
CPython 2.6.5:
------------------------------------------------
elapsed time : 964.23ms
Total packets : 110450
packets/s : 114547.49
As you can see, in this situation the performance increase is rather
significant. CPython still holds the advantage with a fair margin though.
Regards,
Sébastien
Le 20 février 2012 06:38, Antonio Cuni <[email protected]
<mailto:[email protected]>> a écrit :
On 02/20/2012 12:59 PM, Sébastien Volle wrote:
Hello Antonio,
Thank you for the update. I'll try and run a long running capture.
Several
days worth of ARP packets should be enough to maximize JIT effect I
suppose.
I'll keep you updated.
to amortize the JIT warmup cost, it's probably enough to have a benchmark
which runs for few seconds. No clue how many days of ARP packets are
needed for that, though :-).
ciao,
Anto
_______________________________________________
pypy-dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pypy-dev
