[Rubygems-developers] Size of gem index

Nick Sieger nicksieger at gmail.com
Wed Aug 29 11:10:24 EDT 2007


The gem index yaml file is starting to get pretty big.  Folks are
reporting Ruby's memory size gets in the range of 128-150MB when
loading up the index.  Does anyone else think this is starting to get
problematic?

It's especially a problem for JRuby since we need to specify the
memory size of the Java VM up front, so as the gem index grows,
eventually JRuby gem install fails with OutOfMemoryErrors.  It seems
wasteful to us to simply hike the max memory of the VM up to 512MB
(currently the max is 256, but gem install is starting to err
consistently for some even at that level).

Would something like a two-tier index work, with the main yaml/yaml.Z
just containing a list of all available gems/versions with pointers to
individual gemspec files available on the web server, or could gem
even get by w/o the gemspec before a gem is actually downloaded and
installed?

Or is the gem index not something to be mucked with at this stage?

Cheers,
/Nick


More information about the Rubygems-developers mailing list