You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running bundle exec rubocop is a magnitude slower than running rubocop for me.
I'm not sure where this might come from, but I do not experience it with other commands like cane, rails_best_practices or brakeman.
cane 0,34s user 0,01s system 93% cpu 0,378 total
bundle exec cane 1,25s user 0,04s system 99% cpu 1,295 total
rubocop 2,78s user 0,87s system 94% cpu 3,868 total
bundle exec rubocop 95,85s user 3,80s system 99% cpu 1:40,10 total
Is it just me or can you confirm this?
The text was updated successfully, but these errors were encountered:
Yep, I can confirm this. My preliminary analysis shows that the syntax check is problematic - it starts the ruby interpreter with -wc which is pretty fast without bundler, but terribly slow with it.
For some reason running `bundle exec rubocop`
slows down the start of the ruby interpreter (used with `-wc`)
tenfold. Until we figure what's causing this slowdown it's best
not to run syntax checks if we detect bundler's presence. See #64 for
more details.
Running bundle exec rubocop is a magnitude slower than running rubocop for me.
I'm not sure where this might come from, but I do not experience it with other commands like cane, rails_best_practices or brakeman.
cane 0,34s user 0,01s system 93% cpu 0,378 total
bundle exec cane 1,25s user 0,04s system 99% cpu 1,295 total
rubocop 2,78s user 0,87s system 94% cpu 3,868 total
bundle exec rubocop 95,85s user 3,80s system 99% cpu 1:40,10 total
Is it just me or can you confirm this?
The text was updated successfully, but these errors were encountered: