2 ms·

The slowness of brew isnt ruby's fault. They don't keep a local cache of the taps, but instead searches for taps using an API that interfaces with github and se

• aasasd 8y ago
  It's not limited by network speed because I have HOMEBREW_NO_GITHUB_API and HOMEBREW_NO_AUTO_UPDATE enabled. It's not like I just today stumbled into the problem. Brew's not even consuming much system cpu time during `brew search`, despite hogging a core for a full minute. Even just `brew help` takes almost 10 sec cold.
  • wilg 8y ago
    Are you using JRuby or something? 10 seconds is too long. > time brew help > brew help 0.55s user 0.26s system 96% cpu 0.849 total
    • aasasd 8y ago
      Regular Ruby 2.5.1. I do have a throttled CPU due to no battery in the MacBook, but I still have Python and other stuff to compare, and Brew (or Ruby) definitely does something wrong on my machine. It's hugely CPU-bound without a particular reason for being so.
      • wilg 8y ago
        Weird. I'd guess Brew because MRI Ruby tends to have pretty good boot times.