<?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: Why is Google so Fast?</title>
	<atom:link href="http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/</link>
	<description>News, articles and all things HttpWatch</description>
	<pubDate>Thu, 11 Mar 2010 19:29:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Httpwatch Blog</title>
		<link>http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/comment-page-1/#comment-7211</link>
		<dc:creator>Httpwatch Blog</dc:creator>
		<pubDate>Sat, 06 Jun 2009 09:45:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/#comment-7211</guid>
		<description>Yes, Google does some clever things to make its search query fast, but if they didn't also pay attention to front end issues such as page size, round trips and caching all that effort will be wasted.

Steve Souders (Google's chief performance engineer) has a 'Performance Golden Rule':

"80-90% of the end-user response time is spent on the front-end"

See slide #8 of his 'Higher Performance Websites' talk:

http://www.slideshare.net/w3guru/high-performance-websites-by-souders-steve-presentation

This blog post acknowledges the power of Google's distributed super-computer, but then goes on to show what they also did on the front end to ensure that search pages load as fast as possible.</description>
		<content:encoded><![CDATA[<p>Yes, Google does some clever things to make its search query fast, but if they didn&#8217;t also pay attention to front end issues such as page size, round trips and caching all that effort will be wasted.</p>
<p>Steve Souders (Google&#8217;s chief performance engineer) has a &#8216;Performance Golden Rule&#8217;:</p>
<p>&#8220;80-90% of the end-user response time is spent on the front-end&#8221;</p>
<p>See slide #8 of his &#8216;Higher Performance Websites&#8217; talk:</p>
<p><a href="http://www.slideshare.net/w3guru/high-performance-websites-by-souders-steve-presentation" rel="nofollow">http://www.slideshare.net/w3guru/high-performance-websites-by-souders-steve-presentation</a></p>
<p>This blog post acknowledges the power of Google&#8217;s distributed super-computer, but then goes on to show what they also did on the front end to ensure that search pages load as fast as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/comment-page-1/#comment-7210</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sat, 06 Jun 2009 09:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/#comment-7210</guid>
		<description>Wait.. no.. this is rubbish, sorry.
What you've said is true and it *will* reduce load on servers, but it won't increase the speed for the end user by much.
Google rely on complicated search algorithms and a complex mix of hardware and software to query such a massive database, so quickly.
There is talk that parts of the database are always loaded in RAM, and Google uses a custom filesystem.
Those are things that will actually make a difference for the end user, not reducing the number of requests (and remember, the website servers will be different to the servers that query the database).</description>
		<content:encoded><![CDATA[<p>Wait.. no.. this is rubbish, sorry.<br />
What you&#8217;ve said is true and it *will* reduce load on servers, but it won&#8217;t increase the speed for the end user by much.<br />
Google rely on complicated search algorithms and a complex mix of hardware and software to query such a massive database, so quickly.<br />
There is talk that parts of the database are always loaded in RAM, and Google uses a custom filesystem.<br />
Those are things that will actually make a difference for the end user, not reducing the number of requests (and remember, the website servers will be different to the servers that query the database).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaz</title>
		<link>http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/comment-page-1/#comment-1381</link>
		<dc:creator>Gaz</dc:creator>
		<pubDate>Sat, 16 Aug 2008 22:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/#comment-1381</guid>
		<description>That image keeps popping up in the top left hand corner of all my google searches, over the content ( or google logo to be more exact "top left" ) Sometimes it appears multiple times at various points down the page.

I should point out that Im using IE8 in quirks mode, but still, very annoying. I thought I had some kind of strange spyware...

Doesnt happen in Firefox either just IE8 ( Quirks mode for IE7, Im sure its probably just a strange beta issue )</description>
		<content:encoded><![CDATA[<p>That image keeps popping up in the top left hand corner of all my google searches, over the content ( or google logo to be more exact &#8220;top left&#8221; ) Sometimes it appears multiple times at various points down the page.</p>
<p>I should point out that Im using IE8 in quirks mode, but still, very annoying. I thought I had some kind of strange spyware&#8230;</p>
<p>Doesnt happen in Firefox either just IE8 ( Quirks mode for IE7, Im sure its probably just a strange beta issue )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Clark</title>
		<link>http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/comment-page-1/#comment-373</link>
		<dc:creator>Jordan Clark</dc:creator>
		<pubDate>Tue, 20 May 2008 21:59:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.httpwatch.com/2007/11/05/why-is-google-so-fast/#comment-373</guid>
		<description>Excellent article, very well researched. However, Google is an extreme case - they exist in a very competitive market. I would not advocate this way of coding for the average website; their code flies in the face of most modern coding standards.

Then again, it's never done their bank balance any harm!</description>
		<content:encoded><![CDATA[<p>Excellent article, very well researched. However, Google is an extreme case - they exist in a very competitive market. I would not advocate this way of coding for the average website; their code flies in the face of most modern coding standards.</p>
<p>Then again, it&#8217;s never done their bank balance any harm!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
