Hi. I'm having a problem with bulk updating the gem index on one of my VPS such that it doesn't seem likely to complete (it didn't finish in a little over 8hrs).
The ruby process eats all available memory and most, although not all, of the swap. CPU usage appeared minimal although the load average crept up. There is nothing else on the system competing for memory or cpu while this was going on. I narrowed the problem down to SourceIndex#convert_specs: YAML.load(reduce_specs(yaml_spec)) and tried directly using:: curl -o yaml http://gems.rubyforge.org/yaml irb require 'yaml' YAML.load( File.open( 'yaml' ) ) This uses a lot of CPU until free ram is exhausted (with ruby between 70-75mb), then CPU use drops to almost nothing while the process acretes swap space. The VPS has 96mb ram + 128mb of swap. I was a bit surprised to see that the yaml file is 10mb given how routinely gem seems to bulk updating. Has this file been recently poisoned with something huge? Or has it just grown this big? I had someone else, using a VPS with 128mb of RAM, try updating and he reported similar problems. I'd welcome any suggestions on how to get bulk-update working again. Regards, Matt -- Matt Mower :: http://matt.blogs.it/ _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
