On Aug 18, 2007, at 23:21, Eric Hodel wrote: > 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. > > How much RAM is it using? I see about 120MB max with a bulk update > on OS X.
Second data point, ~20 minutes and ~70MB resident on a machine that should be at least an order of magnitude, possibly two, slower than yours. CPU: Geode(TM) Integrated Processor by National Semi (266.66-MHz 586- class CPU) Origin = "Geode by NSC" Id = 0x540 Stepping = 0 Features=0x808131<FPU,TSC,MSR,CX8,CMOV,MMX> real memory = 134217728 (128 MB) avail memory = 126078976 (120 MB) $ /usr/bin/time -l gem list -r *** REMOTE GEMS *** Bulk updating Gem source index for: http://gems.rubyforge.org [...] 1223.66 real 508.13 user 62.21 sys 71700 maximum resident set size 3 average shared memory size 34417 average unshared data size 127 average unshared stack size 158228 page reclaims 51651 page faults 0 swaps 13 block input operations 40 block output operations 9 messages sent 1291 messages received 52739 signals received 51681 voluntary context switches 142100 involuntary context switches -- 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
