PyPy.js: Now faster than CPython

Re:PyPy.js: Now faster than CPython by panarky on Tuesday May 06, 2014 @11:53AM (#7705205)

I get 157K/sec in the terminal and 309K/sec in Chrome.

As the article says, Chrome's performance shows wide variation, even after JIT warmup. It's ranging from 50K/sec to 320K/sec. Bizarre.

[ Parent | on HN ]

Re:PyPy.js: Now faster than CPython by azakai on Tuesday May 06, 2014 @01:36PM (#7705930)

JITs are great but can be unpredictable, that's probably the cause. As mentioned in the article, JITs vs AOT have upsides and downsides.

[ Parent | on HN ]

Re:PyPy.js: Now faster than CPython by steveklabnik on Tuesday May 06, 2014 @02:15PM (#7706172)

Doesn't Chrome specifically _not_ optimize asm.js, as well? Wonder if that has anything to do with it.

[ Parent | on HN ]

Re:PyPy.js: Now faster than CPython by zurn on Tuesday May 06, 2014 @03:39PM (#7706637)

It doesn't special case the asm.js JS subset same way as Firefox does, but V8 guys are paying attention to optimizing asm.js-style code.

[ Parent | on HN ]