Peter Brant wrote:
I recently had the same problem (with Ruby trunk though). Changing
#!/usr/bin/env jruby -J-Xmx384M
to
#!/usr/bin/env jruby -J-Xmx784M
fixed it for me (why JRuby is using so much memory in this case may
still be worth investigating though...)
Unfortunately, though we do use a bit more memory than MRI for reading
the gem spec, we're not entirely to blame for memory issues. The gem
spec is simply growing very quickly.
When I run a gem installation under MRI, it gets close to 200MB of
memory used as well. We're not as efficient as we could be for the
in-memory representation of objects and YAML, but the problem is that
the index is too large.
There's an update coming soon to RubyGems that will shrink the in-memory
size significantly. Hopefully we'll be able to include that in JRuby 1.1
and 1.0.2.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
