Active Record shares all the benefits and drawbacks of ORMs in general. You'll have a much easier time using it if you avoid making these 4 small mistakes.
N+1 queries are quick to sneak in and can wreak havoc on performance. This approach will help you find them quickly, write the test, and preload correctly.
Using code generation for your Rails utility scripts (like importing demo data into production) that can then be executed remotely (no need to deploy).
What if we used Active Record to build the query we want for the count of each child record, then used a named scope to nicely place that as a sub-select?
One-liners can be piped into the heroku run console command—what about longer scripts you write locally and want to execute in a remote Heroku environment?