Comments on: Ruby on rails development tips http://blogs.smarteguru.com/ruby-on-rails/ruby-on-rails-development-tips/ Just another WordPress weblog Tue, 09 Mar 2010 10:08:35 +0500 http://wordpress.org/?v=2.8.2 hourly 1 By: List of Rails Tips http://blogs.smarteguru.com/ruby-on-rails/ruby-on-rails-development-tips/comment-page-1/#comment-54 List of Rails Tips Mon, 15 Sep 2008 18:47:27 +0000 http://blogs.smarteguru.com/?p=203#comment-54 [...] An interesting list of Rails tips to wander through. [...] [...] An interesting list of Rails tips to wander through. [...]

]]> By: rick http://blogs.smarteguru.com/ruby-on-rails/ruby-on-rails-development-tips/comment-page-1/#comment-48 rick Sun, 14 Sep 2008 14:12:15 +0000 http://blogs.smarteguru.com/?p=203#comment-48 Have you done benchmarks to prove that dynamic finders (like find_by_*) are really that much slower? ActiveRecord generates the method in method_missing once, and then after that it's like calling a regular method. But I suppose if that kind of speed is really necessary for you, you could change this: Person.find_by_sql(”SELECT person.height WHERE person.name = ‘JoeyJoeJoe’”) to: connection.select_value "SELECT person.height WHERE person.name = ‘JoeyJoeJoe’” AR::Base.find_by_sql will instantiate a model, even for your single field. I'm a little curious about your comment on dev boxes being faster than production boxes. In my experience (with engine yard at least), it's the complete opposite. However, queries with hundreds of thousands of rows are definitely much slower than my local tables with just 5. But I've found that apps with indexed tables, as you suggest, spend more time rendering the view than fetching from the database. Have you done benchmarks to prove that dynamic finders (like find_by_*) are really that much slower? ActiveRecord generates the method in method_missing once, and then after that it’s like calling a regular method.

But I suppose if that kind of speed is really necessary for you, you could change this:

Person.find_by_sql(”SELECT person.height WHERE person.name = ‘JoeyJoeJoe’”)

to:

connection.select_value “SELECT person.height WHERE person.name = ‘JoeyJoeJoe’”

AR::Base.find_by_sql will instantiate a model, even for your single field.

I’m a little curious about your comment on dev boxes being faster than production boxes. In my experience (with engine yard at least), it’s the complete opposite. However, queries with hundreds of thousands of rows are definitely much slower than my local tables with just 5. But I’ve found that apps with indexed tables, as you suggest, spend more time rendering the view than fetching from the database.

]]>