<?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"
	>
<channel>
	<title>Comments on: The effect of using Rails fragment caching</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Thu, 04 Dec 2008 04:23:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ruby on Rails Optimizing Performance &#124; lonerunners.net</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-818037</link>
		<dc:creator>Ruby on Rails Optimizing Performance &#124; lonerunners.net</dc:creator>
		<pubDate>Wed, 29 Oct 2008 11:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-818037</guid>
		<description>[...] The effect of using Rails fragment caching - Goes over the performance boost of using fragment caching. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The effect of using Rails fragment caching - Goes over the performance boost of using fragment caching. [&#8230;]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Juixe TechKnow &#187; Rails Performance Link Fest</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-190977</link>
		<dc:creator>Juixe TechKnow &#187; Rails Performance Link Fest</dc:creator>
		<pubDate>Wed, 28 Feb 2007 15:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-190977</guid>
		<description>[...] Rails Performance Tips Common Performance Problems in Rails - Pros and con between SQLSessionStore and MemChacheStore session containers, tips on optimizing queries, and general information regarding how to avoid slow helpers. The Adventures of Scaling: Stage 1, Stage 2, Stage 3, Stage 4 - A detailed explanation a Rails production architecture. Optimizing Rails Resource Usage - A short list of top Rails optimization tips, which include the proper use of caching. Sustainable Performance with Ruby on Rails - A 58 page PDF presentation describing railsbench, caching, session performance, and efficient Ruby code. Rails performance tips - A discussion on eager loading, excluding unnecessary columns, indexing database columns, and caching. Top 10 Ruby on Rails performance tips - Provides great tips to optimize your ruby code and how to handle finders. Performance related changes in Rails 1.1 - Discussion of performance enhancements in rails 1.1. Rails performance and caching, Part 2 - A discussing of Rails performance using caching. Stefan Kaes - Rails Performance - RubyConf 2006 conference notes on the Rails Performance presentation given by Stefan Kaes. Stefen Kaes - Optimizing Rails - Another post on the Rails 2006 presentation by Stefan Kaes on Rails Performance. Rails performance with FastCGI and Apache - A blog post on performance with Apache. Rails Performance Tool Box - A list of tools that come in handy when optimizing a Ruby on Rails application, which include query analyzer, query trace, and mtop. Rails Caching Documentation - Documentation for action, page, and fragment caching. The effect of using Rails fragment caching - Goes over the performance boost of using fragment caching. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Rails Performance Tips Common Performance Problems in Rails - Pros and con between SQLSessionStore and MemChacheStore session containers, tips on optimizing queries, and general information regarding how to avoid slow helpers. The Adventures of Scaling: Stage 1, Stage 2, Stage 3, Stage 4 - A detailed explanation a Rails production architecture. Optimizing Rails Resource Usage - A short list of top Rails optimization tips, which include the proper use of caching. Sustainable Performance with Ruby on Rails - A 58 page PDF presentation describing railsbench, caching, session performance, and efficient Ruby code. Rails performance tips - A discussion on eager loading, excluding unnecessary columns, indexing database columns, and caching. Top 10 Ruby on Rails performance tips - Provides great tips to optimize your ruby code and how to handle finders. Performance related changes in Rails 1.1 - Discussion of performance enhancements in rails 1.1. Rails performance and caching, Part 2 - A discussing of Rails performance using caching. Stefan Kaes - Rails Performance - RubyConf 2006 conference notes on the Rails Performance presentation given by Stefan Kaes. Stefen Kaes - Optimizing Rails - Another post on the Rails 2006 presentation by Stefan Kaes on Rails Performance. Rails performance with FastCGI and Apache - A blog post on performance with Apache. Rails Performance Tool Box - A list of tools that come in handy when optimizing a Ruby on Rails application, which include query analyzer, query trace, and mtop. Rails Caching Documentation - Documentation for action, page, and fragment caching. The effect of using Rails fragment caching - Goes over the performance boost of using fragment caching. [&#8230;]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: On Web Apps &#187; Blog Archive &#187; Wisdom of Rails Wizards Study in Best ActiveRecord and Fragment Caching Store</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-129443</link>
		<dc:creator>On Web Apps &#187; Blog Archive &#187; Wisdom of Rails Wizards Study in Best ActiveRecord and Fragment Caching Store</dc:creator>
		<pubDate>Tue, 19 Dec 2006 12:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-129443</guid>
		<description>[...] One of the great things about Rails is that when you hit a DB/rendering performance bottleneck, you can often alleviate it with caching. If page caching is not an option (for example, most of your pageviews are from authenticated users), fragment caching is also a great option which can give you just the exact HTML or partial that you need. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] One of the great things about Rails is that when you hit a DB/rendering performance bottleneck, you can often alleviate it with caching. If page caching is not an option (for example, most of your pageviews are from authenticated users), fragment caching is also a great option which can give you just the exact HTML or partial that you need. [&#8230;]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: dasil003</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-53967</link>
		<dc:creator>dasil003</dc:creator>
		<pubDate>Mon, 11 Sep 2006 21:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-53967</guid>
		<description>I think the other optimizations you mention at the end would not even be worth the effort.

SELECTing fewer columns doesn't normally speed up the database.  I guess if your database is on a slow link or your selecting a ton of data you might eliminate some overhead, but I think the speed improvement would usually be negligible.

The second optimization of using helpers instead of url_for (link_to) depends mostly on the performance of the routing code, which I haven't looked at all that closely.  I guess I've heard one or two complaints about it in the past, but it probably also depends on the complexity of your routes.rb file.  

Before doing any optimization I'd do some profiling first.  And always keep &lt;a href="http://en.wikipedia.org/wiki/Amdahl's_law" rel="nofollow"&gt;Amdahl's&lt;/a&gt; law in mind.  In most web applications the database is the bottleneck, and aside from judicious use of ActiveRecord and a deep understanding of SQL, fragment caching is gonna be your next line of attack.</description>
		<content:encoded><![CDATA[<p>I think the other optimizations you mention at the end would not even be worth the effort.</p>
<p>SELECTing fewer columns doesn&#8217;t normally speed up the database.  I guess if your database is on a slow link or your selecting a ton of data you might eliminate some overhead, but I think the speed improvement would usually be negligible.</p>
<p>The second optimization of using helpers instead of url_for (link_to) depends mostly on the performance of the routing code, which I haven&#8217;t looked at all that closely.  I guess I&#8217;ve heard one or two complaints about it in the past, but it probably also depends on the complexity of your routes.rb file.  </p>
<p>Before doing any optimization I&#8217;d do some profiling first.  And always keep <a href="http://en.wikipedia.org/wiki/Amdahl's_law" rel="nofollow">Amdahl&#8217;s</a> law in mind.  In most web applications the database is the bottleneck, and aside from judicious use of ActiveRecord and a deep understanding of SQL, fragment caching is gonna be your next line of attack.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: timlucas</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-46878</link>
		<dc:creator>timlucas</dc:creator>
		<pubDate>Mon, 21 Aug 2006 15:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-46878</guid>
		<description>It's interesting to note though that Ruby 2 should speed things up dramatically, as (&lt;a href="http://redhanded.hobix.com/cult/youKnowKoichiSanYeahKoichiAtNamikilabInTokyoKnowWhatHeSApparentlyTheChosenSonShiGetALoadOfThat.html" rel="nofollow"&gt;by the looks of it&lt;/a&gt;) &lt;a href="http://www.atdot.net/yarv/" rel="nofollow"&gt;YARV&lt;/a&gt; will be the core engine</description>
		<content:encoded><![CDATA[<p>It&#8217;s interesting to note though that Ruby 2 should speed things up dramatically, as (<a href="http://redhanded.hobix.com/cult/youKnowKoichiSanYeahKoichiAtNamikilabInTokyoKnowWhatHeSApparentlyTheChosenSonShiGetALoadOfThat.html" rel="nofollow">by the looks of it</a>) <a href="http://www.atdot.net/yarv/" rel="nofollow">YARV</a> will be the core engine</p>]]></content:encoded>
	</item>
	<item>
		<title>By: chrisb</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-46873</link>
		<dc:creator>chrisb</dc:creator>
		<pubDate>Mon, 21 Aug 2006 14:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-46873</guid>
		<description>Fair point, thanks for the answer :)</description>
		<content:encoded><![CDATA[<p>Fair point, thanks for the answer :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: timlucas</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-46865</link>
		<dc:creator>timlucas</dc:creator>
		<pubDate>Mon, 21 Aug 2006 13:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-46865</guid>
		<description>The above two lines from the log aren't benchmarks that can be looked usefully outside of comparing them to one another.

Rails scales well on both the server and code complexity sides of the equation, but the base-line performance can be less than applications written on other languages, frameworks and platforms (but does that really say anything... as there's always &lt;em&gt;something&lt;/em&gt; that's going to perform faster than what you're using).

Really, it's too hard to answer your question as it's so open-ended. I will say though that Rails is written on the tenet that servers are cheap, brains are expensive and that performance that's "good enough" for 99% of people is ok. There's plenty of room for the other 1% of people to optimise if they have the need.</description>
		<content:encoded><![CDATA[<p>The above two lines from the log aren&#8217;t benchmarks that can be looked usefully outside of comparing them to one another.</p>
<p>Rails scales well on both the server and code complexity sides of the equation, but the base-line performance can be less than applications written on other languages, frameworks and platforms (but does that really say anything&#8230; as there&#8217;s always <em>something</em> that&#8217;s going to perform faster than what you&#8217;re using).</p>
<p>Really, it&#8217;s too hard to answer your question as it&#8217;s so open-ended. I will say though that Rails is written on the tenet that servers are cheap, brains are expensive and that performance that&#8217;s &#8220;good enough&#8221; for 99% of people is ok. There&#8217;s plenty of room for the other 1% of people to optimise if they have the need.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: chrisb</title>
		<link>http://www.sitepoint.com/blogs/2006/08/21/the-effect-of-using-rails-fragment-caching/#comment-46861</link>
		<dc:creator>chrisb</dc:creator>
		<pubDate>Mon, 21 Aug 2006 12:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1682#comment-46861</guid>
		<description>What is the overall performance of Rails like then?  Both of those benchmarks look fairly poor considering that page isnt exactly doing complicated stuff?</description>
		<content:encoded><![CDATA[<p>What is the overall performance of Rails like then?  Both of those benchmarks look fairly poor considering that page isnt exactly doing complicated stuff?</p>]]></content:encoded>
	</item>
</channel>
</rss>
