<?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: Improving Blog Latency to Benefit Readers</title>
	<atom:link href="http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/</link>
	<description>Linux, politics, and other interesting things</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:09:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/comment-page-1/#comment-17321</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Thu, 18 Dec 2008 10:19:47 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=739#comment-17321</guid>
		<description>http://www.phpmyvisites.us/

Bubba: I believe that Webalizer is as good as you can get by analysing web logs.  Javascript is supposed to give more accurate results (the above URL has an alternative to the popular Google offering).

As for referrer spam, this is why the default configuration is that Webalizer will not generate output with links to referrers.

Of course it&#039;s best to password protect access to your web stats anyway.</description>
		<content:encoded><![CDATA[<p><a href="http://www.phpmyvisites.us/" rel="nofollow">http://www.phpmyvisites.us/</a></p>
<p>Bubba: I believe that Webalizer is as good as you can get by analysing web logs.  Javascript is supposed to give more accurate results (the above URL has an alternative to the popular Google offering).</p>
<p>As for referrer spam, this is why the default configuration is that Webalizer will not generate output with links to referrers.</p>
<p>Of course it&#8217;s best to password protect access to your web stats anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bubba</title>
		<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/comment-page-1/#comment-17304</link>
		<dc:creator>Bubba</dc:creator>
		<pubDate>Tue, 16 Dec 2008 14:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=739#comment-17304</guid>
		<description>I DONOT like WebAlizer. 
Main reasons:
1) Not very correct stats
2) Refspam through webalizer logs

Refspam is popular in my country, and in case they make it more often the site with WebAlizer may me ddosed.

Thats what i think</description>
		<content:encoded><![CDATA[<p>I DONOT like WebAlizer.<br />
Main reasons:<br />
1) Not very correct stats<br />
2) Refspam through webalizer logs</p>
<p>Refspam is popular in my country, and in case they make it more often the site with WebAlizer may me ddosed.</p>
<p>Thats what i think</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/comment-page-1/#comment-15694</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 03 Sep 2008 15:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=739#comment-15694</guid>
		<description>What does ikiwiki lack that you need?  You might consider reporting a feature request.</description>
		<content:encoded><![CDATA[<p>What does ikiwiki lack that you need?  You might consider reporting a feature request.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/comment-page-1/#comment-15604</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Sun, 31 Aug 2008 17:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=739#comment-15604</guid>
		<description>Chris: Thanks for the advice, I&#039;ll have to check that out.

Eric: Oh, that is not how I understood it - but on reviewing the web site it seems to be explained reasonably clearly.  It seems that my preconceptions of what a Unix system is overrode Amazon&#039;s description of the service.

The storage cost for EBS is a mere 10 cents per month per GB (which is nothing for the amount of data I have).  The cost for IO is an issue.  I&#039;ll have to try and measure the amount of IO for a database to determine what it would be.  While 10 cents for a million IO requests doesn&#039;t sound like much, I really don&#039;t know how much database operation I can get for a million IO requests.</description>
		<content:encoded><![CDATA[<p>Chris: Thanks for the advice, I&#8217;ll have to check that out.</p>
<p>Eric: Oh, that is not how I understood it &#8211; but on reviewing the web site it seems to be explained reasonably clearly.  It seems that my preconceptions of what a Unix system is overrode Amazon&#8217;s description of the service.</p>
<p>The storage cost for EBS is a mere 10 cents per month per GB (which is nothing for the amount of data I have).  The cost for IO is an issue.  I&#8217;ll have to try and measure the amount of IO for a database to determine what it would be.  While 10 cents for a million IO requests doesn&#8217;t sound like much, I really don&#8217;t know how much database operation I can get for a million IO requests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Moore</title>
		<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/comment-page-1/#comment-15602</link>
		<dc:creator>Eric Moore</dc:creator>
		<pubDate>Sun, 31 Aug 2008 16:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=739#comment-15602</guid>
		<description>the status with EC2 storage is this, you get an image, and as long as you don&#039;t terminate that instance, your storage is persistent.  But if you terminate the instance (or it&#039;s terminated for you, by say, machine failure), the data is lost.  If you&#039;re just going to leave an EC2 instance up 24/7 it&#039;s much like any other virtual host, although it&#039;s not backed up or anything like that.

Regarding the best way to store comments, strikes me the best way is just write them into a static page and serve that as well.  Most of your accesses are going to be of the &quot;show me all the comments to this post&quot; anyway.  (you can always also have a database that allows searching, but i&#039;d write the main comment page to disk and just serve that puppy)</description>
		<content:encoded><![CDATA[<p>the status with EC2 storage is this, you get an image, and as long as you don&#8217;t terminate that instance, your storage is persistent.  But if you terminate the instance (or it&#8217;s terminated for you, by say, machine failure), the data is lost.  If you&#8217;re just going to leave an EC2 instance up 24/7 it&#8217;s much like any other virtual host, although it&#8217;s not backed up or anything like that.</p>
<p>Regarding the best way to store comments, strikes me the best way is just write them into a static page and serve that as well.  Most of your accesses are going to be of the &#8220;show me all the comments to this post&#8221; anyway.  (you can always also have a database that allows searching, but i&#8217;d write the main comment page to disk and just serve that puppy)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Samuel</title>
		<link>http://etbe.coker.com.au/2008/08/31/improving-blog-latency-benefit-readers/comment-page-1/#comment-15587</link>
		<dc:creator>Chris Samuel</dc:creator>
		<pubDate>Sun, 31 Aug 2008 12:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=739#comment-15587</guid>
		<description>Register another vote for wp_super_cache here, it&#039;s got some nice features, the main one being that for visitors who have a WP cookie set a page is cached as  a straight HTML page meaning there&#039;s no need to invoke the PHP engine to produce it, so Apache can just sendfile() it to them.</description>
		<content:encoded><![CDATA[<p>Register another vote for wp_super_cache here, it&#8217;s got some nice features, the main one being that for visitors who have a WP cookie set a page is cached as  a straight HTML page meaning there&#8217;s no need to invoke the PHP engine to produce it, so Apache can just sendfile() it to them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

