50% slowdown in t/compilers/opsc/02-parse-all-ops.t ?

[James E Keenan]

Vasily Chekalkin wrote:
> Hello.
>
> On Mon, Mar 14, 2011 at 8:12 AM, Andy Dougherty<doughera at lafayette.edu>  wrote:
>> I don't know if this slowdown is expected or significant, but it's
>> certainly quite noticeable.
>
> It's kind of "expected" due "opsc_full_parse" merge. We now
> semantically parse ops bodies.
>

Let me ask the obvious devil's advocate question:  Is this another case 
where Parrot's getting "better" entails Parrot's getting slower?

What are the implications of this for, say, Rakudo's startup and 
execution times?

kid51