`bundle update` has a considerable performance impact on medium sized projects. #609

postmodern opened this Issue Aug 25, 2010 · 9 comments


None yet
6 participants

postmodern commented Aug 25, 2010

I attempted to run bundle update for ronin-gen on 1.9.2-p0, which has a fair amount of dependencies. bundle update would update any used git repositories, download the RubyGems specs.yml file, and begin resolving the dependencey graph for ronin-gen. Except, that bundle update was so inefficient or hit an infinite loop, I had to stop it after hitting the 57 minutes mark.

Steps to reproduce.

  1. git clone git://github.com/ronin-ruby/ronin-gen.git
  2. cd ronin-gen && bundle install
  3. time bundle update

indirect commented Aug 25, 2010

Thanks for the report. We'll look into it.

whatwho commented Nov 3, 2010

can approve that. we changed rails gem version to 2.3.10 in our rails app, and in our rails gems as well (so we had to change also our gem versions). after i edited the gemfile neither bundle install nor bundle update can run. we managed the upgrade by editing gemfile.lock to the new gem versions.

I'm experiencing this too, also with ruby 1.9.2-p0. Can't recall if I've seen it on 1.8.7 (I use REE).

aselder commented Nov 8, 2010

Also seeing this on a Rails 2.3.8 project under Ruby 1.8.7

aselder commented Nov 8, 2010

Looking at the process information while the command was running, I see the ruby process using 1 thread and 100% CPU usage.


indirect commented Nov 9, 2010

@aselder, if you want detailed information on what's going on, try running DEBUG_RESOLVER=true bundle update. That will print out information about what the resolver is doing.

aselder commented Nov 9, 2010

@indirect, I did and saw it got stuck in an infinite loop. See the seperate issue I filed (#829).

Looks like the dependency tree from metric_fu threw it in an infinite loop.


rohit commented Mar 21, 2012

Was this resolved in bundler 1.1?


postmodern commented Mar 21, 2012

Definitely resolved in 1.1. Closing this.

postmodern closed this Mar 21, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment