One of the things that’s really annoying about everybody and their dog blogging the shit out of the Internet is that most people only ever scratch the surface. Why bother with properly researching the cause of an issue or questioning one’s metrics when we can just run ruby-prof, let it generate a graph and say “Look, that chart clearly shows that something is wrong”? Then again, I guess it’s an instant gratification thing: You get a thrill about discovering that something’s wrong and nobody else seems to have found out about it yet so you have to tell the world.

Hell, I’m getting angry. 🙂 What I really wanted to say: Thanks for clarifying! 😀

Something like this should never take 55 seconds on a modern machine for any sane combination of interpreter and algorithm. Something is very wrong here…

Yes, although the gains should not be significant unless you are removing a
lot of routes.

One question. Say I am using only index method of my resource “users”. So in the routes I will have :only => [:index]. I believe this will reduce the amount of memory rails consumes.

Now based on your blog would it be accurate to say this will reduce the boot time since regex
do not need to be generated for other 6 verbs.

I have used ruby-prof on 1.8.7 and 1.9.2. You can easily profile a request by creating a middleware that executes ruby-prof during @app.call(env) and prints out the result.

I have used ruby-prof on 1.8.7 and 1.9.2. You can easily profile a request
by creating a middleware that executes ruby-prof during @app.call() and
prints out the result.