Comments on: Performance tips for Ruby on rails application

By: John Taylor

John Taylor — Thu, 23 Apr 2009 23:26:23 +0000

I found your blog on Google. I’ve bookmarked it and will watch out for your next blog post.

By: Danielle

Danielle — Wed, 01 Apr 2009 16:29:02 +0000

I’ve never given this a try, but I think it’s about time I do.

By: Patrick

Patrick — Thu, 11 Sep 2008 04:27:58 +0000

Nothing substitutes for benchmarks. Things that ought to be fast are sometimes slow. Things that ought to be slow are sometimes fast.

But don’t trust the benchmarks. Sometimes I’d return to my machine to find the *same query* running in less than a second instead of over a minute. I was using SQL_NO_CACHE, so I think background optimisation is responsible here. Since the database was very large, it’s possible that OSX’s virtual memory management was also interfering.

By: Chuck Bergeron

Chuck Bergeron — Tue, 09 Sep 2008 14:32:33 +0000

Thanks for the post!

In regards to point #2, there’s some built-in helpers for caching in Rails 2.1 which are super helpful: http://railscasts.com/episodes/115-caching-in-rails-2-1

By: Pluron

Pluron — Mon, 08 Sep 2008 18:50:35 +0000

passing a block to a method of ActiveRecord::Associations::HasManyAssociation instance and its friends chews up the memory.

For example, a single call to association.select { |record| record.new_record? } can allocate up to 10K of memory depending on the association size.

By: Bamboo

Bamboo — Mon, 08 Sep 2008 18:44:36 +0000

Tweaking the database lets you make huge gains in performance without modifying your complex application.