<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: YouTube Scalability Talk</title>
	<link>http://kylecordes.com/2007/07/12/youtube-scalability/</link>
	<description>Kyle Cordes's Software Site</description>
	<pubDate>Sun, 20 Jul 2008 18:43:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Frank Malina</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-22243</link>
		<pubDate>Thu, 03 Jul 2008 14:09:59 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-22243</guid>
					<description>Very concise reading.
I've just wrote a similar article on the &lt;a href="http://vizualbod.com/make-your-own-youtube-03072008" rel="nofollow"&gt;video streaming applications&lt;/a&gt;, although it's from the top of my head.</description>
		<content:encoded><![CDATA[<p>Very concise reading.<br />
I&#8217;ve just wrote a similar article on the <a href="http://vizualbod.com/make-your-own-youtube-03072008" rel="nofollow">video streaming applications</a>, although it&#8217;s from the top of my head.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: nelix</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10593</link>
		<pubDate>Sun, 22 Jul 2007 22:29:55 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10593</guid>
					<description>A good read, psyco is makes multiple versions of each block for different types (python is dynamically typed, which is slow) so the type bottlenecks are removed at run time, to some extent anyway. At least that's how I understand it.</description>
		<content:encoded><![CDATA[<p>A good read, psyco is makes multiple versions of each block for different types (python is dynamically typed, which is slow) so the type bottlenecks are removed at run time, to some extent anyway. At least that&#8217;s how I understand it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: nsfun</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10520</link>
		<pubDate>Wed, 18 Jul 2007 13:31:23 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10520</guid>
					<description>and youtube uses netscaler ... a small detail :)</description>
		<content:encoded><![CDATA[<p>and youtube uses netscaler &#8230; a small detail <img src='http://kylecordes.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Charles Iliya Krempeaux</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10497</link>
		<pubDate>Tue, 17 Jul 2007 14:42:26 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10497</guid>
					<description>Alot of this sounds like the scalability techniques we used to build an ad network...  although we were using PHP and not Python.

We were doing about 1000 hits per second on average... although it could be very spikey traffic... so it could shoot way up, beyond that, on a spike.  (It almost like a getting DDoS'ed all the time.)

Believe it or not... there's scalability problems (and solutions) beyond those listed here.  Interesting stuff to work on, IMO.

The more and more you have to scale... things like database accesses become to "expensive", and you have to remove them.  Table JOIN's need to be taken out too (... to "expensive").

In-memory databases sometime become a solution.

And logging things in a file... instead of INSERT'ing into or UPDATE'ing a database also become necessary.

ReiserFS was a help.

Also... sometimes you need data centers spread around the world... with slightly different versions of your system optimized for those locations.


-- Charles</description>
		<content:encoded><![CDATA[<p>Alot of this sounds like the scalability techniques we used to build an ad network&#8230;  although we were using PHP and not Python.</p>
<p>We were doing about 1000 hits per second on average&#8230; although it could be very spikey traffic&#8230; so it could shoot way up, beyond that, on a spike.  (It almost like a getting DDoS&#8217;ed all the time.)</p>
<p>Believe it or not&#8230; there&#8217;s scalability problems (and solutions) beyond those listed here.  Interesting stuff to work on, IMO.</p>
<p>The more and more you have to scale&#8230; things like database accesses become to &#8220;expensive&#8221;, and you have to remove them.  Table JOIN&#8217;s need to be taken out too (&#8230; to &#8220;expensive&#8221;).</p>
<p>In-memory databases sometime become a solution.</p>
<p>And logging things in a file&#8230; instead of INSERT&#8217;ing into or UPDATE&#8217;ing a database also become necessary.</p>
<p>ReiserFS was a help.</p>
<p>Also&#8230; sometimes you need data centers spread around the world&#8230; with slightly different versions of your system optimized for those locations.</p>
<p>&#8211; Charles
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: metale</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10479</link>
		<pubDate>Mon, 16 Jul 2007 16:33:26 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10479</guid>
					<description>Simply Superb...!!</description>
		<content:encoded><![CDATA[<p>Simply Superb&#8230;!!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: geekmaster grok</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10468</link>
		<pubDate>Mon, 16 Jul 2007 06:33:17 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10468</guid>
					<description>such an excellent read.  thanks.</description>
		<content:encoded><![CDATA[<p>such an excellent read.  thanks.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: spect</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10466</link>
		<pubDate>Mon, 16 Jul 2007 05:55:45 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10466</guid>
					<description>its a rare pleasure to gain this kind of architecture and engineering insight from some of the larger web based companies.  used to be easier, but i dont live in the bay area anymore, wish i could find more info like this.

thanks</description>
		<content:encoded><![CDATA[<p>its a rare pleasure to gain this kind of architecture and engineering insight from some of the larger web based companies.  used to be easier, but i dont live in the bay area anymore, wish i could find more info like this.</p>
<p>thanks
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Adarsh</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10464</link>
		<pubDate>Mon, 16 Jul 2007 04:48:20 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10464</guid>
					<description>Excellent Discovery !</description>
		<content:encoded><![CDATA[<p>Excellent Discovery !
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Seo Sanghyeon</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10463</link>
		<pubDate>Mon, 16 Jul 2007 04:32:49 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10463</guid>
					<description>psyco is not a Python-&#62;C compiler. It's Python JIT (although not exactly).</description>
		<content:encoded><![CDATA[<p>psyco is not a Python-&gt;C compiler. It&#8217;s Python JIT (although not exactly).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chris</title>
		<link>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10458</link>
		<pubDate>Mon, 16 Jul 2007 01:23:08 +0000</pubDate>
		<guid>http://kylecordes.com/2007/07/12/youtube-scalability/#comment-10458</guid>
					<description>This is awesome.  Thanks for taking the time to expose the underpinnings! :D

Very interesting to see that they're using Lighttpd.  I have to agree with your comment on nginx ... perhaps they'll move to it in the future.</description>
		<content:encoded><![CDATA[<p>This is awesome.  Thanks for taking the time to expose the underpinnings! <img src='http://kylecordes.com/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>Very interesting to see that they&#8217;re using Lighttpd.  I have to agree with your comment on nginx &#8230; perhaps they&#8217;ll move to it in the future.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
