[pypy-dev] Poor performance with custom bytecode

Antonio Cuni anto.cuni at gmail.com
Fri Feb 17 14:29:01 CET 2012

On 02/17/2012 02:27 PM, Timothy Baldridge wrote:
>> In pypy we have a custom opcode to call methods, which is much faster than
>> LOAD_ATTR/CALL_FUNCTION. See e.g. how this piece of code gets compiled:
> Excellent! I was unaware of this. Just last night I started
> abstracting some bytecode generation to support both 2.6 and 2.7, so
> it won't be hard to slot in improvements for pypy.
>  From there, I'll start looking into jitviewer.

I suggest to look at the jitviewer before doing this. I might be wrong and 
LOAD_ATTR/CALL_FUNCTION be efficient enough, I don't know.

Also note that you should hit reply-all when replying, else you send the email 
only to the author and not to the ML (I re-added pypy-dev in CC).


More information about the pypy-dev mailing list