<?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: Boost Your Web site Performance</title>
	<atom:link href="http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 25 Jan 2012 00:41:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mikhailov Anatoly</title>
		<link>http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/comment-page-1/#comment-14947</link>
		<dc:creator>Mikhailov Anatoly</dc:creator>
		<pubDate>Wed, 17 Dec 2008 04:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/#comment-14947</guid>
		<description>Mod_deflate in apache2 is pretty much the same as mod_gzip in apache1.3, and mod_deflate is included with the apache2 source package. Both modules allow compressing of the apache server on the fly

http://railsgeek.com/2008/12/16/apache2-httpd-improving-performance-mod_deflate-gzip</description>
		<content:encoded><![CDATA[<p>Mod_deflate in apache2 is pretty much the same as mod_gzip in apache1.3, and mod_deflate is included with the apache2 source package. Both modules allow compressing of the apache server on the fly</p>
<p><a href="http://railsgeek.com/2008/12/16/apache2-httpd-improving-performance-mod_deflate-gzip" rel="nofollow">http://railsgeek.com/2008/12/16/apache2-httpd-improving-performance-mod_deflate-gzip</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zuborg</title>
		<link>http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/comment-page-1/#comment-12608</link>
		<dc:creator>zuborg</dc:creator>
		<pubDate>Mon, 27 Oct 2008 18:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/#comment-12608</guid>
		<description>I would also recommend to use this online free performance testing tool - http://Site-Perf.com/ 

It measure loading speed of page and it’s requisites (images/js/css) like browsers do and shows nice detailed chart - so you can easily spot bottlenecks. It&#039;s very detailed and accurate, supports a lot of features like Keep-Alive and HTTP-compression. 

Also useful feature is that this tool can measure quality of internet link of your server.</description>
		<content:encoded><![CDATA[<p>I would also recommend to use this online free performance testing tool &#8211; <a href="http://Site-Perf.com/" rel="nofollow">http://Site-Perf.com/</a> </p>
<p>It measure loading speed of page and it’s requisites (images/js/css) like browsers do and shows nice detailed chart &#8211; so you can easily spot bottlenecks. It&#8217;s very detailed and accurate, supports a lot of features like Keep-Alive and HTTP-compression. </p>
<p>Also useful feature is that this tool can measure quality of internet link of your server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Klaus</title>
		<link>http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/comment-page-1/#comment-3201</link>
		<dc:creator>Klaus</dc:creator>
		<pubDate>Tue, 27 Nov 2007 20:11:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/#comment-3201</guid>
		<description>Mike: thanks very much for clarification, I really got confused by that whole ETags issue...

PS: That&#039;s why I love working for Yahoo!: brilliant and bright people (who even visit my blog) ;-)</description>
		<content:encoded><![CDATA[<p>Mike: thanks very much for clarification, I really got confused by that whole ETags issue&#8230;</p>
<p>PS: That&#8217;s why I love working for Yahoo!: brilliant and bright people (who even visit my blog) <img src='http://www.klauskomenda.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike West</title>
		<link>http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/comment-page-1/#comment-3200</link>
		<dc:creator>Mike West</dc:creator>
		<pubDate>Tue, 27 Nov 2007 19:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.klauskomenda.com/archives/2007/11/10/boost-your-website-performance/#comment-3200</guid>
		<description>Jeff&#039;s advice about ETags is, in my opinion, poorly expressed with double or triple negatives confusing the issue.  He says &quot;So unless you run a server farm, you should ignore this guidance.&quot;  What he _means_ is &quot;Klaus, you only have a single server: use ETags.&quot;  In fact, they really _only_ work (on Apache and IIS) in your specific circumstance.  :)

ETags are a problem at Yahoo! because each page is served from a multitude of servers.  Because of the way an ETag is generated, it contains a machine-specific identifier (the inode of the file on the disk for Apache, or the configuration change number for IIS); the ETag for resource X on server 1 is different from the tag for that same resource on server 2.  This equals massive fail.

Your case is different: you only have one server, and the ETag for a specific resource will always remain the same.  If you turn on ETags, therefore, you&#039;ll trade in at least a few heavy `200 OK` responses for lightweight `304 Not Modified` responses.  You&#039;ll be happier, your server will be happier, and life in general will be better.</description>
		<content:encoded><![CDATA[<p>Jeff&#8217;s advice about ETags is, in my opinion, poorly expressed with double or triple negatives confusing the issue.  He says &#8220;So unless you run a server farm, you should ignore this guidance.&#8221;  What he _means_ is &#8220;Klaus, you only have a single server: use ETags.&#8221;  In fact, they really _only_ work (on Apache and IIS) in your specific circumstance.  <img src='http://www.klauskomenda.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>ETags are a problem at Yahoo! because each page is served from a multitude of servers.  Because of the way an ETag is generated, it contains a machine-specific identifier (the inode of the file on the disk for Apache, or the configuration change number for IIS); the ETag for resource X on server 1 is different from the tag for that same resource on server 2.  This equals massive fail.</p>
<p>Your case is different: you only have one server, and the ETag for a specific resource will always remain the same.  If you turn on ETags, therefore, you&#8217;ll trade in at least a few heavy `200 OK` responses for lightweight `304 Not Modified` responses.  You&#8217;ll be happier, your server will be happier, and life in general will be better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

