On May 30, 2007, at 11:48 , Eric Hodel wrote: > Working with the source cache creates a giant object tree. > > Loading the YAML file creates two very large Strings and a giant > object tree. > > Loading a handful of updates creates a handful or two of very small > object trees and Strings. > > While its hard to capture the latter, it does take much less memory > than the former. > > The problem is being worked on right now.
I just committed a change that seems to cut memory use by about 40ish %. There was a phase that was munging the output to deal with an old yaml bug and was creating quite a bit of memory. Removing it dropped my memory consumption from 112meg to 73meg. We could drop a tad more if we nuked the part of the cache for the source we were currently bulk loading, but it only equated to about 10 meg in my experiments. _______________________________________________ Rubygems-developers mailing list Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
