1

using the railties patch described in this post: slow rails stack, i'm noticing that the step "set_routes_reloader" is regularly taking upwards of 3 seconds.

is this expected? if not, what might i be doing wrong and/or how do i go about figuring out if i'm doing something wrong, etc.

Community
  • 1
  • 1
whatbird
  • 1,552
  • 1
  • 14
  • 25

1 Answers1

0

In our case the problem was that we were defining too many routes. The set_routes_reloader step loads your routes (as you might guess). We got a lot of mileage by adding the appropriate :except/:only arguments.

Something that may help you is the traceroute gem which provides you a list of routes that do not have an associated controller action. I wrote a one-time script to process our traceroute output and update our routes.rb file. You can find it here.

Simon Chiang
  • 835
  • 1
  • 8
  • 14