On Aug 18, 2007, at 14:28, Farhan Ahmad wrote: > I have been looking into why 'gem update' has been taking hours > and > hours on my computer to complete. Given that it's only a 700Mhz > machine > with 512MB RAM I still didn't think that would qualify it for such > slow > updates. Also, a normal system update, i.e. ArchLinux's pacman > updates, > takes only a minute to download and parse. So, I started playing > around > with the source and boiled everything down to the YAML.load call in > source_index.rb. Later I found out that this was already being > discussed in a few posts [0][1] on this mailing list. Ryan D., > thanks a > lot for removing the reduce_specs call [1] because that helped with > the > performance. Unfortunately, the problem is still there. > > I have looked through the mailing list archive and seen some other > threads but can't figure out where this issue currently stands. Is > there already a plan for rectifying this?
How much RAM is it using? I see about 120MB max with a bulk update on OS X. -- Poor workers blame their tools. Good workers build better tools. The best workers get their tools to do the work for them. -- Syndicate Wars _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
