Charles Oliver Nutter wrote:
It's probably safe to assume that almost all of the core types we
autoconvert are suffering from this performance hit right now, because
they all rely on a generic piece of code with a bunch of stacked object
comparisons to do conversion. And the change I made would
Charles Oliver Nutter wrote:
The odd thing about this is that there should be very little challenge
in making return values quickly rubify to an appropriate type. We know
the return value from a given method isn't going to change, and we know
exactly how to box it or wrap it. So what's the deal
I've been running a few tests. JI performance stinks pretty bad.
Here's numbers from the existing test, which takes two byteslists via JI
and appends one to the other. No new objects created, other than
internally the array for the bytelist growing. And performance isn't too
bad, about 2x a no
