Speed Up Your Performance With N+1, Don’t Kill It

N + 1 is better in this case by a mere implementation coincidence.

Doing caches only on the views can be seen as incomplete: you also can cache query results by wrapping them into Rails.cache (with custom expiration times/logic etc).

There’s no excuse for n+1, particularly when AR and various tooling (bullet, sql_logging) makes it easy to fight it!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.