<?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: GrabPERF: Search Index Weekly Results (Sep 12-18, 2005)</title>
	<atom:link href="http://newestindustry.org/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/feed/" rel="self" type="application/rss+xml" />
	<link>http://newestindustry.org/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/</link>
	<description>Web Performance, Branding, and Social Media</description>
	<lastBuildDate>Wed, 17 Mar 2010 01:50:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: smp</title>
		<link>http://newestindustry.org/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/comment-page-1/#comment-558</link>
		<dc:creator>smp</dc:creator>
		<pubDate>Tue, 20 Sep 2005 00:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://crazycanuck.wordpress.com/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/#comment-558</guid>
		<description>&lt;br/&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;However, PubSub will still come up on top; Google doesn&#039;t bother to compress their ATOM feeds.&lt;br/&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;Ouch!&lt;br/&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;smp</description>
		<content:encoded><![CDATA[<p>However, PubSub will still come up on top; Google doesn&#8217;t bother to compress their ATOM feeds.</p>
<p>Ouch!</p>
<p>smp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Wyman</title>
		<link>http://newestindustry.org/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/comment-page-1/#comment-557</link>
		<dc:creator>Bob Wyman</dc:creator>
		<pubDate>Mon, 19 Sep 2005 22:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://crazycanuck.wordpress.com/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/#comment-557</guid>
		<description>&lt;br/&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;I&#039;d like to suggest that you include a second test for Google BlogSearch to make the comparison to PubSub a bit more fair.  What you&#039;re retrieving from PubSub is an Atom feed, not a full HTML page. Typically, HTML pages can be filled with all sorts of junk that isn&#039;t present in Atom feeds. Thus, the Google BlogSearch numbers may be getting dragged down by them having to transfer more data or do more formatting of the output.  So, what I&#039;d like to suggest is that you include a second &quot;Atom&quot; search test for Google BS that would look like this:&lt;br/&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;&lt;a href=&quot;http://blogsearch.google.com/blogsearch_feeds?scoring=dq=%22new+york%22num=32output=atom%3Cbr/&quot;&gt;http://blogsearch.google.com/blogsearch_feeds?s...&lt;/a&gt;&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;Since PubSub always returns 32 results (if present) it makes sense to adjust the Google BlogSearch item &quot;num&quot; to be 32. Admittedly, there would still be a difference between PubSub and Google BlogSearch since GoogleBS only returns summaries while PubSub returns full posts. However, this difference in payload size might get lost in the wash.&lt;br/&gt;&lt;br&gt;&lt;br/&gt;&lt;br&gt;bob wyman&lt;br/&gt;&lt;br&gt;&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to suggest that you include a second test for Google BlogSearch to make the comparison to PubSub a bit more fair.  What you&#8217;re retrieving from PubSub is an Atom feed, not a full HTML page. Typically, HTML pages can be filled with all sorts of junk that isn&#8217;t present in Atom feeds. Thus, the Google BlogSearch numbers may be getting dragged down by them having to transfer more data or do more formatting of the output.  So, what I&#8217;d like to suggest is that you include a second &#8220;Atom&#8221; search test for Google BS that would look like this:</p>
<p><a href="http://blogsearch.google.com/blogsearch_feeds?scoring=dq=%22new+york%22num=32output=atom%3Cbr/"></a><a href="http://blogsearch.google.com/blogsearch_feeds?s.." rel="nofollow">http://blogsearch.google.com/blogsearch_feeds?s..</a>.&gt;</p>
<p>Since PubSub always returns 32 results (if present) it makes sense to adjust the Google BlogSearch item &#8220;num&#8221; to be 32. Admittedly, there would still be a difference between PubSub and Google BlogSearch since GoogleBS only returns summaries while PubSub returns full posts. However, this difference in payload size might get lost in the wash.</p>
<p>bob wyman</p>
<p></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smp</title>
		<link>http://newestindustry.org/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/comment-page-1/#comment-229</link>
		<dc:creator>smp</dc:creator>
		<pubDate>Mon, 19 Sep 2005 19:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://crazycanuck.wordpress.com/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/#comment-229</guid>
		<description>Ok the test is added.&lt;br /&gt;
&lt;br /&gt;
However, PubSub will still come up on top; Google doesn&#039;t bother to compress their ATOM feeds.&lt;br /&gt;
&lt;br /&gt;
Ouch!&lt;br /&gt;
&lt;br /&gt;
smp</description>
		<content:encoded><![CDATA[<p>Ok the test is added.</p>
<p>However, PubSub will still come up on top; Google doesn&#8217;t bother to compress their ATOM feeds.</p>
<p>Ouch!</p>
<p>smp</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Wyman</title>
		<link>http://newestindustry.org/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/comment-page-1/#comment-228</link>
		<dc:creator>Bob Wyman</dc:creator>
		<pubDate>Mon, 19 Sep 2005 17:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://crazycanuck.wordpress.com/2005/09/19/grabperf-search-index-weekly-results-sep-12-18-2005/#comment-228</guid>
		<description>I&#039;m a little surprised to see that the Google Blogsearch numbers aren&#039;t better than they are. The site certainly feels much snappier than the numbers would indicate.&lt;br /&gt;
&lt;br /&gt;
I&#039;d like to suggest that you include a second test for Google BlogSearch to make the comparison to PubSub a bit more fair.  What you&#039;re retrieving from PubSub is an Atom feed, not a full HTML page. Typically, HTML pages can be filled with all sorts of junk that isn&#039;t present in Atom feeds. Thus, the Google BlogSearch numbers may be getting dragged down by them having to transfer more data or do more formatting of the output.  So, what I&#039;d like to suggest is that you include a second &quot;Atom&quot; search test for Google BS that would look like this:&lt;br /&gt;
&lt;br /&gt;
http://blogsearch.google.com/blogsearch_feeds?scoring=d&amp;q=&quot;new+york&quot;&amp;num=32&amp;output=atom&lt;br /&gt;
&lt;br /&gt;
Since PubSub always returns 32 results (if present) it makes sense to adjust the Google BlogSearch item &quot;num&quot; to be 32. Admittedly, there would still be a difference between PubSub and Google BlogSearch since GoogleBS only returns summaries while PubSub returns full posts. However, this difference in payload size might get lost in the wash.&lt;br /&gt;
&lt;br /&gt;
bob wyman&lt;br /&gt;
&lt;br /&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;m a little surprised to see that the Google Blogsearch numbers aren&#8217;t better than they are. The site certainly feels much snappier than the numbers would indicate.</p>
<p>I&#8217;d like to suggest that you include a second test for Google BlogSearch to make the comparison to PubSub a bit more fair.  What you&#8217;re retrieving from PubSub is an Atom feed, not a full HTML page. Typically, HTML pages can be filled with all sorts of junk that isn&#8217;t present in Atom feeds. Thus, the Google BlogSearch numbers may be getting dragged down by them having to transfer more data or do more formatting of the output.  So, what I&#8217;d like to suggest is that you include a second &#8220;Atom&#8221; search test for Google BS that would look like this:</p>
<p><a href="http://blogsearch.google.com/blogsearch_feeds?scoring=d&amp;q=" rel="nofollow">http://blogsearch.google.com/blogsearch_feeds?scoring=d&amp;q=</a>&#8220;new+york&#8221;&amp;num=32&amp;output=atom</p>
<p>Since PubSub always returns 32 results (if present) it makes sense to adjust the Google BlogSearch item &#8220;num&#8221; to be 32. Admittedly, there would still be a difference between PubSub and Google BlogSearch since GoogleBS only returns summaries while PubSub returns full posts. However, this difference in payload size might get lost in the wash.</p>
<p>bob wyman</p>
]]></content:encoded>
	</item>
</channel>
</rss>
