Why is gem so slow

Hmm, weird, the SSH session just terminated. But I'm still connected to other sessions on that machine. Very very strange Add a comment.

Active Oldest Votes. Improve this answer. Thanks, I think that'll help! Documentation install is always so extremely slow, which sounds silly. That's because the documentation is generated from the RDoc comments in the.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.

Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Already on GitHub? Sign in to your account. Hello everyone. I have a problem with gem installation. It is really very slow. I can't understand why. With bundler this problem not exist. The text was updated successfully, but these errors were encountered:.

Is this something that happens constantly or just once? Sorry, something went wrong. It is happend not only qbindings and faker. It is happend for any gem when i try to install.

Can you please share the output of gem env , as well as the —verbose output of installing a gem? Hei Mracobes9! According to , this has been fixed in rubygems 3. Are you able to confirm this by upgrading rubygems with gem update --system , and see if the issue disappears? This problem is disappear in rubygems 3. I am also experiencing this problem. My gem version is 3.

Running on Windows. Any ideas what the culprit might be? That one in particular seems to take several minutes. However, gem install minima just took about half a minute and it was already installed :. Was the most of the time spend at Building native extensions. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. Asked 11 years, 11 months ago. Active 7 years, 1 month ago. Viewed 2k times. Improve this question. Add a comment. Active Oldest Votes. The solution from Doc Snuggles really works. But it should be notice that your gem command maybe living in a gemset, that is: rvm info grep gem will tell you where the gem script lives.

Then edit it and add the magic line before any other require : require 'resolv-replace'.