array_access.pir on Parrot's from 0.5 - trunk (r42903)

Jonathan Leto jaleto at gmail.com
Mon Dec 7 05:47:06 UTC 2009


Howdy,

Sadly, the results look the same with --count=100:

http://gist.github.com/250648

Duke



On Sun, Dec 6, 2009 at 9:02 PM, Jonathan Leto <jaleto at gmail.com> wrote:
> Howdy,
>
> I just realized that I gist'ed the output for a run with a --count of
> 1 (which I do to see if stuff segaults/parses), instead of the normal
> 100. I am running the benchmark again and will post updated results
> soon.
>
> Duke
>
> PS: Thanks to pmichaud++ for noticing
>
> On Sun, Dec 6, 2009 at 7:59 PM, Jonathan Leto <jaleto at gmail.com> wrote:
>> Howdy,
>>
>> Looks like our array access is twice as slow in trunk then in 1.8.0.
>> This is probably seriously hurting us due to the amount of arrays PCC
>> creates during parsing.
>>
>> http://gist.github.com/250599
>>
>> PS: Most benchmarks from now on will only go back to 0.5.0, since
>> testing Parrot's before that often requires mangling benchmarks to get
>> them to parse.
>>
>> Duke
>>
>>
>>
>> --
>> Jonathan "Duke" Leto
>> jonathan at leto.net
>> http://leto.net
>>
>
>
>
> --
> Jonathan "Duke" Leto
> jonathan at leto.net
> http://leto.net
>



-- 
Jonathan "Duke" Leto
jonathan at leto.net
http://leto.net


More information about the parrot-dev mailing list