Mitchell N Charity <[EMAIL PROTECTED]> wrote:
> Patch attached.
I've renamed the files to oofib sp running parrotbench -b='^oo' gets
then all. Thanks, applied.
> My optimized parrot ran it a factor of 2x slower than my perls, 3x than
> my ruby, with my pythons in between. Unoptimized was just a
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Looks like it may be time to investigate things further. A method
> cache is probably the next thing in line to do.
Yep. The OO-version of fib spends by far the most time in callmethcc.
fib/fibA (3/4th of the calls) need 4 hash lookups currently.
leo
Looks like it may be time to investigate things further. A method
cache is probably the next thing in line to do.
I didn't see a benchmark for method lookup and calling, so I modified
a copy of fib to bounce back and forth between a class and its parent.
Patch attached.
My optimized parr
And while it helps... it doesn't help enough. Objects are now a bare
PMC array, nice and simple. (In fact, back to the original PMC array
implementation almost. Go figure) This speeds up object creation
rather a bit, and with an --optimize build we only get beaten a lot
by perl 5 and python on
