[sams99]

Sure, but what is stopping you from choosing a more efficient architecture for your Rails app?

For example, we use pgbouncer transaction pooling, so our connection counts are low. Tons of caching is done in NGINX and first middleware in the stack, we are not afraid of using SQL where needed for performance reasons and so on.

For an application that is taking data from a database and turning into JSON or HTML, spending 50% of the time in the database is not really a crime of bad architecture. In fact even when we built Stack Overflow in superfast C# we often saw a similar breakdown.

I just really object to the sentiment of "abandon ship" Y is 12x faster.