<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Making Gravatar fast again</title>
	<atom:link href="http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/</link>
	<description>Barry on WordPress.com</description>
	<lastBuildDate>Fri, 25 Dec 2009 22:26:34 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#160; varnish reverse proxy server&#160;by&#160;Video Sharing Script</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-10514</link>
		<dc:creator>&#160; varnish reverse proxy server&#160;by&#160;Video Sharing Script</dc:creator>
		<pubDate>Wed, 09 Apr 2008 07:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-10514</guid>
		<description>[...] Read about wordpress.com scaling at http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Read about wordpress.com scaling at <a href="http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/" rel="nofollow">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kenpem</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-10506</link>
		<dc:creator>kenpem</dc:creator>
		<pubDate>Sun, 23 Mar 2008 15:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-10506</guid>
		<description>Now we just need the rest of the world to adopt gravatar as a standard and we&#039;re happy ;)</description>
		<content:encoded><![CDATA[<p>Now we just need the rest of the world to adopt gravatar as a standard and we&#8217;re happy <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trent</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-8247</link>
		<dc:creator>Trent</dc:creator>
		<pubDate>Sat, 10 Nov 2007 23:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-8247</guid>
		<description>The IT world is pretty lucky that you put up the architecture and strategies that you use Barry on all these different setups!   Sometimes though I think you might need a glossary of terms for us people who don&#039;t speak wrangler, but great stuff, none the less!</description>
		<content:encoded><![CDATA[<p>The IT world is pretty lucky that you put up the architecture and strategies that you use Barry on all these different setups!   Sometimes though I think you might need a glossary of terms for us people who don&#8217;t speak wrangler, but great stuff, none the less!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-8101</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Tue, 06 Nov 2007 10:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-8101</guid>
		<description>Bruno,

Currently it is manual because the automatic failover portion is not complete yet, but it should be finished this week.  The basic idea is that each datacenter will also have a server that serves DNS requests.  Each datacenter&#039;s DNS server will only return its own IP when queried.  There are some additional monitoring scripts that check the application and cache server and make sure all is functioning normally, otherwise stop the DNS service.  In the case of a server or datacenter outage, the IP of the failed node will not be returned via DNS so traffic will automatically failover to the other location.  There are DNS TTLs to deal with, but they can be set very low so impact is minimal.  

I will probably write a separate post on this setup with more details once its complete.</description>
		<content:encoded><![CDATA[<p>Bruno,</p>
<p>Currently it is manual because the automatic failover portion is not complete yet, but it should be finished this week.  The basic idea is that each datacenter will also have a server that serves DNS requests.  Each datacenter&#8217;s DNS server will only return its own IP when queried.  There are some additional monitoring scripts that check the application and cache server and make sure all is functioning normally, otherwise stop the DNS service.  In the case of a server or datacenter outage, the IP of the failed node will not be returned via DNS so traffic will automatically failover to the other location.  There are DNS TTLs to deal with, but they can be set very low so impact is minimal.  </p>
<p>I will probably write a separate post on this setup with more details once its complete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-8061</link>
		<dc:creator>Bruno</dc:creator>
		<pubDate>Mon, 05 Nov 2007 01:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-8061</guid>
		<description>Hi, interesting post.

So, you have a cache &amp; application server in each of your datacenter.

Do you manually fallback to the other one if one datacenter is in trouble by changing the DNS entry?

Or you have something more automatic?</description>
		<content:encoded><![CDATA[<p>Hi, interesting post.</p>
<p>So, you have a cache &amp; application server in each of your datacenter.</p>
<p>Do you manually fallback to the other one if one datacenter is in trouble by changing the DNS entry?</p>
<p>Or you have something more automatic?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donncha&#8217;s Tuesday Links at Holy Shmoly!</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7903</link>
		<dc:creator>Donncha&#8217;s Tuesday Links at Holy Shmoly!</dc:creator>
		<pubDate>Tue, 30 Oct 2007 09:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7903</guid>
		<description>[...] reveals some of the details behind what powers Gravatar [...]</description>
		<content:encoded><![CDATA[<p>[...] reveals some of the details behind what powers Gravatar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7898</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Tue, 30 Oct 2007 04:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7898</guid>
		<description>James,

We are using &lt;a href=&quot;http://munin.projects.linpro.no/&quot; rel=&quot;nofollow&quot;&gt;Munin&lt;/a&gt; to graph the data.  There are Varnish graphing plugins &lt;a href=&quot;http://varnish.projects.linpro.no/browser/trunk/varnish-tools/munin&quot; rel=&quot;nofollow&quot;&gt;available&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>James,</p>
<p>We are using <a href="http://munin.projects.linpro.no/" rel="nofollow">Munin</a> to graph the data.  There are Varnish graphing plugins <a href="http://varnish.projects.linpro.no/browser/trunk/varnish-tools/munin" rel="nofollow">available</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7897</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Tue, 30 Oct 2007 04:05:54 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7897</guid>
		<description>John,

The working set is only about 1GB (lucky us!)

Having an infinite expiry would require cache invalidation which is not something that we are currently doing on Gravatar.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>The working set is only about 1GB (lucky us!)</p>
<p>Having an infinite expiry would require cache invalidation which is not something that we are currently doing on Gravatar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links for Mon 29 Oct 2007 &#124; Joseph Scott's Blog</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7892</link>
		<dc:creator>Links for Mon 29 Oct 2007 &#124; Joseph Scott's Blog</dc:creator>
		<pubDate>Tue, 30 Oct 2007 00:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7892</guid>
		<description>[...] Making Gravatar fast again &#124; Barry on WordPress - Details from Barry on what Automattic is using to run Gravatar.  Tags: gravatar [...]</description>
		<content:encoded><![CDATA[<p>[...] Making Gravatar fast again | Barry on WordPress &#8211; Details from Barry on what Automattic is using to run Gravatar.  Tags: gravatar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ArtLung Blog &#187; Misc, Misc, everywhere&#8230; and not a drop to drink</title>
		<link>http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7881</link>
		<dc:creator>ArtLung Blog &#187; Misc, Misc, everywhere&#8230; and not a drop to drink</dc:creator>
		<pubDate>Mon, 29 Oct 2007 15:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://barry.wordpress.com/2007/10/26/making-gravatar-fast-again/#comment-7881</guid>
		<description>[...] moved Gravatar to their infrastructure which has gone well, the blog High Scalability pointed out Making Gravatar Fast Again. Cool stuff, and will help them avoid &#8220;crashing hard&#8221; moments. The Gravatar article [...]</description>
		<content:encoded><![CDATA[<p>[...] moved Gravatar to their infrastructure which has gone well, the blog High Scalability pointed out Making Gravatar Fast Again. Cool stuff, and will help them avoid &#8220;crashing hard&#8221; moments. The Gravatar article [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
