Improve slow Rails startup time (rails console, rails server)

Question

I work with several Rails apps, some on Rails 3.2/Ruby 2.0, and some one Rails 2.3/Ruby 1.8.7.

What they have in common is that, as they've grown and added more dependencies/gems, they take longer and longer to start. Development, Test, Production, console, it doesn't matter; some take 60+ seconds.

What is the preferred way to first, profile for what is causing load times to be so slow, and two, improve the load times?

score 19 · Answer 1 · edited May 23 '17 at 11:45

There are a few things that can cause this.

Too many GC passes and general VM shortcomings - See this answer for a comprehensive explanation. Ruby <2.0 has some really slow bits that can dramatically increase load speeds; compiling Ruby with the Falcon or railsexpress patches can massively help that. All versions of MRI Ruby use GC settings by default that are inappropriate for Rails apps.
Many legacy gems that have to be iterated over in order to load files. If you're using bundler, try bundle clean. If you're using RVM, you could try creating a fresh gemset.

As far as profiling goes, you can use ruby-prof to profile what happens when you boot your app. You can wrap config/environment.rb in a ruby-prof block, then use that to generate profile reports of a boot cycle with something like rails r ''. This can help you track down where you're spending the bulk of your time in boot. You can profile individual sections, too, like the bundler setup in boot.rb, or the #initialize! call in environment.rb.

Something you might not be considering is DNS timeouts. If your app is performing DNS lookups on boot, which it is unable to resolve, these can block the process for $timeout seconds (which might be as high as 30 in some cases!). You might audit the app for those, as well.

score 13 · Accepted Answer · edited Oct 05 '20 at 14:33

13

Ryan has a good tutorial about speeding up tests, console, rake tasks: http://railscasts.com/episodes/412-fast-rails-commands?view=asciicast

I have checked every methods there and found "spring" the best. Just run the tasks like:

$ spring rspec

The time for your first run of spring will be same as before, but the second and later will be much faster.

Also, from my experience, there will be time you need to stop spring server and restart when there is weird error, but the chance is rare.

edited Oct 05 '20 at 14:33

Parth Bharadiya

53
7

answered Jul 03 '13 at 01:30

Billy Chan

24,625
4
52
68

1

Thanks, Spring is great! It does break a lot of my rspec/capybara tests though. – professormeowingtons Jul 22 '13 at 02:14
1

Sadly, `spring`, although fast and awesome, definitely hates rspec/capybara. – professormeowingtons Aug 14 '13 at 21:18
@professormeowingtons, why do you say that? I've been using spring for a long time and running rspec everyday and feel good. – Billy Chan Aug 15 '13 at 03:10
This issue, sorry I meant factorygirl not capybara: https://github.com/jonleighton/spring/issues/88 – professormeowingtons Aug 15 '13 at 07:16

score 0 · Answer 3 · answered Jul 02 '13 at 23:46

0

For ruby 2 apps, try zeus - https://github.com/burke/zeus

1.8 apps seem to boot much faster than 1.9, spork might help? http://railscasts.com/episodes/285-spork

answered Jul 02 '13 at 23:46

house9

20,359
8
55
61

1

Neither of those actually helps boot time, they simply checkpoint the app after initial booting so you can spin off forks from a warmed state. While useful, they don't address the OP's question directly. – Chris Heald Jul 02 '13 at 23:49

Improve slow Rails startup time (rails console, rails server)

3 Answers3