[pypy-dev] array performace?

Maciej Fijalkowski fijall at gmail.com
Fri Jul 2 10:19:02 CEST 2010

On Fri, Jul 2, 2010 at 2:17 AM, Armin Rigo <arigo at tunes.org> wrote:
> Hi Fijal,
> On Thu, Jul 01, 2010 at 09:35:17AM -0600, Maciej Fijalkowski wrote:
>> The main reason why _rawffi.Array is slow is that JIT does not look
>> into that module, so there is wrapping and unwrapping going on.
>> Relatively easy to fix I suppose, but _rawffi.Array was not meant to
>> be used like that (array.array looks like a better candidate).
> If you mean "better candidate" for being fast right now, then you missed
> my point: our array.array module is implemented on top of
> _rawffi.Array.  If you mean "better candidate" for being optimizable
> given some work, then yes, I agree that the array module is a good
> target.

By "better candidate" I mean that having JIT see _rawffi might mean
some struggle for it to understand what's going on with raw pointers
and writing array in interp-level would be better.

More information about the Pypy-dev mailing list