I think 1GB is reasonable, and while I run with more if I have it, I don't
have any apps or test suites that will actually run out of heap with 1GB.
My JRuby CI system tests our Rails apps with 1GB.
Wishing for the zillionth time that the JVM had a "target heap" setting :-)
On Tue, Dec 20, 2011 a
Charles Oliver Nutter created JRUBY-6290:
Summary: jruby-dist maven artifact does not publish anything
Key: JRUBY-6290
URL: https://jira.codehaus.org/browse/JRUBY-6290
Project: JRuby
On Mon, Dec 19, 2011 at 9:22 AM, Charles Oliver Nutter
wrote:
> 2. AbstractRubyHash
>
> This is the long-talked-about refactoring of RubyHash into an abstract
> half and an implementation half.
>
> The experiment is here: https://github.com/headius/jruby/tree/abstract_hash
>
> It does not yet comp
On Tue, Dec 20, 2011 at 12:01 PM, Yoko Harada wrote:
> AbstractRubyHash looks good. Once this implementation comes in,
> MapJavaProxy class can have much simpler implementation.
Yeah, I think it would literally have *just* the abstract methods and
perfom as well as Hash or the underlying Map.
>
http://ci.jruby.org/job/rails-master/ is now configured to use 1.9 mode.
We actually have been failing these builds since they switched to 1.9
mode. So we are no less green than before. I think one //n bug away
from getting meaningful results.
-Tom
--
blog: http://blog.enebo.com twitter
Ben Browning created JRUBY-6291:
---
Summary: Closing One Stream From IO.popen4 Results in Stream
Closed Error When Reading Other Streams
Key: JRUBY-6291
URL: https://jira.codehaus.org/browse/JRUBY-6291
Pr
Charles Oliver Nutter created JRUBY-6292:
Summary: Massive perf degradation in pack after ByteList update
Key: JRUBY-6292
URL: https://jira.codehaus.org/browse/JRUBY-6292
Project: JRuby