<?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: Twitter&#8217;s one-to-many scaling impossible?</title>
	<atom:link href="http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/feed/" rel="self" type="application/rss+xml" />
	<link>http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/</link>
	<description>Out In His Elements</description>
	<lastBuildDate>Sat, 27 Feb 2010 01:16:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Crossing the streams - large numbers of Twitter updates</title>
		<link>http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/comment-page-1/#comment-296</link>
		<dc:creator>Crossing the streams - large numbers of Twitter updates</dc:creator>
		<pubDate>Sun, 29 Jun 2008 14:51:57 +0000</pubDate>
		<guid isPermaLink="false">http://solyoung.com/?p=209#comment-296</guid>
		<description>[...] Bilson (@cbilson) had a good description regarding my post about Twitter&#8217;s scaling/architecture challenge. &#8220;Kevin Rose and Leo Laporte tweet at the same time = crossing the [...]</description>
		<content:encoded><![CDATA[<p>[...] Bilson (@cbilson) had a good description regarding my post about Twitter&#8217;s scaling/architecture challenge. &#8220;Kevin Rose and Leo Laporte tweet at the same time = crossing the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sol Young</title>
		<link>http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/comment-page-1/#comment-2883</link>
		<dc:creator>Sol Young</dc:creator>
		<pubDate>Fri, 27 Jun 2008 20:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://solyoung.com/?p=209#comment-2883</guid>
		<description>I don&#039;t think so. They are, or will be, hitting numbers that today&#039;s hardware can&#039;t keep up with. An exponential increase in load is way beyond the growth of Moore&#039;s law.&lt;br&gt;&lt;br&gt;In order to keep their service stable they will have to make changes to the base functionality or impose limitations on maximum followers or following.&lt;br&gt;&lt;br&gt;Facebook capped at 5,000. Since they offer push services, I wonder if this was a calculated decision based on scale.</description>
		<content:encoded><![CDATA[<p>I don&#39;t think so. They are, or will be, hitting numbers that today&#39;s hardware can&#39;t keep up with. An exponential increase in load is way beyond the growth of Moore&#39;s law.</p>
<p>In order to keep their service stable they will have to make changes to the base functionality or impose limitations on maximum followers or following.</p>
<p>Facebook capped at 5,000. Since they offer push services, I wonder if this was a calculated decision based on scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TimWalker</title>
		<link>http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/comment-page-1/#comment-2882</link>
		<dc:creator>TimWalker</dc:creator>
		<pubDate>Fri, 27 Jun 2008 19:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://solyoung.com/?p=209#comment-2882</guid>
		<description>Very interesting. Wish I were more tech-savvy to understand the hardware implications of all of this. At the very least, though -- and even if your numbers are back-of-the-envelope style -- it explains much better for this tech neophyte why &quot;Just add more servers&quot; isn&#039;t necessarily the solution.&lt;br&gt;&lt;br&gt;Can they get around these architecture issues, do you think?</description>
		<content:encoded><![CDATA[<p>Very interesting. Wish I were more tech-savvy to understand the hardware implications of all of this. At the very least, though &#8212; and even if your numbers are back-of-the-envelope style &#8212; it explains much better for this tech neophyte why &#8220;Just add more servers&#8221; isn&#39;t necessarily the solution.</p>
<p>Can they get around these architecture issues, do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sol Young</title>
		<link>http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/comment-page-1/#comment-2492</link>
		<dc:creator>Sol Young</dc:creator>
		<pubDate>Fri, 27 Jun 2008 16:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://solyoung.com/?p=209#comment-2492</guid>
		<description>I don&#039;t think so. They are, or will be, hitting numbers that today&#039;s hardware can&#039;t keep up with. An exponential increase in load is way beyond the growth of Moore&#039;s law.&lt;br&gt;&lt;br&gt;In order to keep their service stable they will have to make changes to the base functionality or impose limitations on maximum followers or following.&lt;br&gt;&lt;br&gt;Facebook capped at 5,000. Since they offer push services, I wonder if this was a calculated decision based on scale.</description>
		<content:encoded><![CDATA[<p>I don&#39;t think so. They are, or will be, hitting numbers that today&#39;s hardware can&#39;t keep up with. An exponential increase in load is way beyond the growth of Moore&#39;s law.</p>
<p>In order to keep their service stable they will have to make changes to the base functionality or impose limitations on maximum followers or following.</p>
<p>Facebook capped at 5,000. Since they offer push services, I wonder if this was a calculated decision based on scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TimWalker</title>
		<link>http://solyoung.com/2008/06/27/twitters-one-to-many-scaling-impossible/comment-page-1/#comment-2491</link>
		<dc:creator>TimWalker</dc:creator>
		<pubDate>Fri, 27 Jun 2008 15:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://solyoung.com/?p=209#comment-2491</guid>
		<description>Very interesting. Wish I were more tech-savvy to understand the hardware implications of all of this. At the very least, though -- and even if your numbers are back-of-the-envelope style -- it explains much better for this tech neophyte why &quot;Just add more servers&quot; isn&#039;t necessarily the solution.&lt;br&gt;&lt;br&gt;Can they get around these architecture issues, do you think?</description>
		<content:encoded><![CDATA[<p>Very interesting. Wish I were more tech-savvy to understand the hardware implications of all of this. At the very least, though &#8212; and even if your numbers are back-of-the-envelope style &#8212; it explains much better for this tech neophyte why &#8220;Just add more servers&#8221; isn&#39;t necessarily the solution.</p>
<p>Can they get around these architecture issues, do you think?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
