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
compiler not handling x += 1 correctly for cases where x hasn't been assigned
-
Key: JRUBY-1216
URL: http://jira.codehaus.org/browse/JRUBY-1216
Project: JRuby
Issue
Hi all,
Since even before JRuby 1.0, My JRuby on Rails app never lasted more
than 24 hours in prod env when while being browsed by Google and Yahoo
bots.
I investigated on this recently, and, while I'm not completely sure,
it seems that JRuby (from 1.0 to head; Java 6u2; Linux 2.6.18) doesn't
l
Hi all,
Since even before JRuby 1.0, My JRuby on Rails app never lasted more
than 24 hours in prod env when while being browsed by Google and Yahoo
bots.
I investigated on this recently, and, while I'm not completely sure,
it seems that JRuby (from 1.0 to head; Java 6u2; Linux 2.6.18) doesn't
l
parsing of float different than cruby (with patch)
--
Key: JRUBY-1215
URL: http://jira.codehaus.org/browse/JRUBY-1215
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
