<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: More Ruby Scaling</title>
	<atom:link href="http://davedupre.com/2007/07/06/more-ruby-scaling/feed/" rel="self" type="application/rss+xml" />
	<link>http://davedupre.com/2007/07/06/more-ruby-scaling/</link>
	<description>Some random thoughts - Go big or stay home!</description>
	<lastBuildDate>Sun, 06 Jun 2010 08:59:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: admin</title>
		<link>http://davedupre.com/2007/07/06/more-ruby-scaling/comment-page-1/#comment-10</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 06 Jul 2007 21:49:05 +0000</pubDate>
		<guid isPermaLink="false">http://davedupre.com/2007/07/06/more-ruby-scaling/#comment-10</guid>
		<description>I use that trick for other things, but I have 30,000+ companies in my database.  The include trick is not efficient.  I keep the companies in a cache.

Mostly, my point is to be aware of all the magic that Ruby is doing.  The easy stuff works great when you start off, but you will want to watch the database calls.</description>
		<content:encoded><![CDATA[<p>I use that trick for other things, but I have 30,000+ companies in my database.  The include trick is not efficient.  I keep the companies in a cache.</p>
<p>Mostly, my point is to be aware of all the magic that Ruby is doing.  The easy stuff works great when you start off, but you will want to watch the database calls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Kieschnick</title>
		<link>http://davedupre.com/2007/07/06/more-ruby-scaling/comment-page-1/#comment-9</link>
		<dc:creator>Josh Kieschnick</dc:creator>
		<pubDate>Fri, 06 Jul 2007 21:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://davedupre.com/2007/07/06/more-ruby-scaling/#comment-9</guid>
		<description>Hey Dave,
Another way of getting around all of the database hits would be to include the other tables in your joins.

In your controller you could have something like @people = Person.find(:all, :include =&gt; :companies

When using active record in your views, it won&#039;t need to make the db call because rails will keep the join information in memory. Depending on how many records there are, you will probably see a significant increase in speed.</description>
		<content:encoded><![CDATA[<p>Hey Dave,<br />
Another way of getting around all of the database hits would be to include the other tables in your joins.</p>
<p>In your controller you could have something like @people = Person.find(:all, :include =&gt; :companies</p>
<p>When using active record in your views, it won&#8217;t need to make the db call because rails will keep the join information in memory. Depending on how many records there are, you will probably see a significant increase in speed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
