<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Esoteric Curio - Comments</title>
    <link>http://www.lethargy.org/~jesus/</link>
    <description>Esoteric Curio - Theo's Contributions to Technological Surreality</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.1 - http://www.s9y.org/</generator>
    <pubDate>Sat, 05 Jul 2008 23:24:36 GMT</pubDate>

    <image>
        <url>http://www.lethargy.org/~jesus/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Esoteric Curio - Comments - Esoteric Curio - Theo's Contributions to Technological Surreality</title>
        <link>http://www.lethargy.org/~jesus/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Theo Schlossnagle: Scalability and concessions</title>
    <link>http://www.lethargy.org/~jesus/archives/122-Scalability-and-concessions.html#c22788</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/122-Scalability-and-concessions.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=122</wfw:comment>

    

    <author>nospam@example.com (Theo Schlossnagle)</author>
    <content:encoded>
    Dan, well played.  You make my point stick.  Those are all excellent questions.  And clearly the &quot;one large database&quot; has a very different usage pattern than the horizontally partitioned one.

My point in all of this: &lt;strong&gt;ask the question&lt;/strong&gt; before jumping to the answer.

For datapoints, the &quot;one big database&quot; averages about 6k transactions/second and peaks around 20k/second.  Very little batched -- that&#039;s done on the &quot;one big datawarehouse&quot;.

As for the horizontally partitioned one... I&#039;d say less transaction right now, but the growth predictions led us down the path of a partitioned approach. 
    </content:encoded>

    <pubDate>Thu, 03 Jul 2008 23:19:08 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/122-guid.html#c22788</guid>
    
</item>
<item>
    <title>Dan Creswell: Scalability and concessions</title>
    <link>http://www.lethargy.org/~jesus/archives/122-Scalability-and-concessions.html#c22787</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/122-Scalability-and-concessions.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=122</wfw:comment>

    

    <author>nospam@example.com (Dan Creswell)</author>
    <content:encoded>
    Mmmm, so you have some interesting raw data - wouldn&#039;t mind a little bit more if you&#039;re game:


....&quot;[You] Can&#039;t use just one database&quot; -- this is a conclusion you should arrive at after analysis.  We have one client that supports 10 million users on a cluster of partitioned databases.  We have another that supports 35 millions users on one database without issue and room for growth.....

How many operations are being performed concurrently by each sets of users?  Are the loads write intensive or read intensive?  How much data do these operations typically touch?

.....My bank supports many more users and transactions than LinkedIn -- and it damn well better have FKs and 100% integrity.  So, while you still may partition in such a fashion that requires a loss of enforced integrity, the decision should be a heavy one.....

What&#039;s your definition for a transaction?  Are these transactions processed in real-time?  Do you batch them?  Are the loads write intensive or read intensive?  How much data do these operations typically touch? 
    </content:encoded>

    <pubDate>Thu, 03 Jul 2008 14:13:26 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/122-guid.html#c22787</guid>
    
</item>
<item>
    <title>Jannis: Scalability and concessions</title>
    <link>http://www.lethargy.org/~jesus/archives/122-Scalability-and-concessions.html#c22786</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/122-Scalability-and-concessions.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=122</wfw:comment>

    

    <author>nospam@example.com (Jannis)</author>
    <content:encoded>
    Thank you, that last sentence made your point very clear &lt;img src=&quot;http://www.lethargy.org/~jesus/templates/default/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; 
    </content:encoded>

    <pubDate>Thu, 03 Jul 2008 07:45:21 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/122-guid.html#c22786</guid>
    
</item>
<item>
    <title>Theo Schlossnagle: Reconnoiter and another platform</title>
    <link>http://www.lethargy.org/~jesus/archives/121-Reconnoiter-and-another-platform.html#c22785</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/121-Reconnoiter-and-another-platform.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=121</wfw:comment>

    

    <author>nospam@example.com (Theo Schlossnagle)</author>
    <content:encoded>
    I looked a little bit.  Their tool looks to have a lot of differences in approach.  None of the differences are wrong and their approach seems pretty well thought out.


We choose to use an RDBMS.  This is not as efficient (but scales with partitioning easily), but allows for complex querying of data.  The distributed, disconnected data collection was foundational for Reconnoiter with a strong approach toward performance.  Additionally, the front-end of reconnoiter is designed to be highly interactive and simple to use -- I didn&#039;t look into the orbitz stuff enough to know that they don&#039;t do this.  Their stuff looks really nice. 
    </content:encoded>

    <pubDate>Wed, 02 Jul 2008 10:55:16 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/121-guid.html#c22785</guid>
    
</item>
<item>
    <title>ashbhai: Reconnoiter and another platform</title>
    <link>http://www.lethargy.org/~jesus/archives/121-Reconnoiter-and-another-platform.html#c22784</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/121-Reconnoiter-and-another-platform.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=121</wfw:comment>

    

    <author>nospam@example.com (ashbhai)</author>
    <content:encoded>
    Theo,
How different is Reconnoiter from the monitoring tools released by Orbitz?
Orbitz Open Sources Monitoring Tools ERMA and Graphite
http://www.infoq.com/news/2008/06/orbitz-opensource-erma 
    </content:encoded>

    <pubDate>Tue, 01 Jul 2008 23:20:54 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/121-guid.html#c22784</guid>
    
</item>
<item>
    <title>ian Holsman: Reconnoiter and another platform</title>
    <link>http://www.lethargy.org/~jesus/archives/121-Reconnoiter-and-another-platform.html#c22783</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/121-Reconnoiter-and-another-platform.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=121</wfw:comment>

    

    <author>nospam@example.com (ian Holsman)</author>
    <content:encoded>
    Looks good Theo.

you might want to investigate some stream processing tools like http://esper.codehaus.org/ to help you with anomaly detection 
    </content:encoded>

    <pubDate>Tue, 01 Jul 2008 20:44:29 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/121-guid.html#c22783</guid>
    
</item>
<item>
    <title>Theo Schlossnagle: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22782</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Theo Schlossnagle)</author>
    <content:encoded>
    In response:

1. That was actually the point.  The old rule of thumb is to maintain about 70% utilization and I&#039;m saying it is time to rethink that paradigm.  You echo my conclusion with using large instances with low utilization &quot;just in case.&quot;  However, if other VMs on the same hardware spike at the same time, you are limited due to over saturation of the underlying hardware.  Heavy use machines typically use all of the hardware anyway.

2.  It takes us far less than 60 minutes to bring online new systems from bare-metal, app install, test and integrate into the load balancer.  So, it&#039;s really the first few minutes I&#039;m interested in solving, the rest is canned.

I think elastic computing make sense the smaller you are.  If I have 4 hosts, the ebb and flow is more dramatic and clouds can help a lot.  When I already have more than a few racks of servers, I have my own elastic computing if I designed the infrastructure correctly.  The premium on fully taxed VMs is pretty significant on the wallet. 
    </content:encoded>

    <pubDate>Tue, 01 Jul 2008 08:59:04 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22782</guid>
    
</item>
<item>
    <title>ElasticHosts: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22781</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (ElasticHosts)</author>
    <content:encoded>
    Theo identifies a real issue, but I believe cloud computing systems do provide a little more help than he gives them credit for. A user of a cloud service such as ElasticHosts or the others has two fallbacks:

1) For the initial response to the spike, the user can indeed set up with &quot;warm&quot; capacity - and this works very well in a cloud computing environment. e.g. they can size their virtual servers for large CPU/RAM with a low base utilization - while they have low usage the hypervisor will share capacity with other VMs, but it is instantly available when the spike hits.

2) Although the spike hits instantly, the higher level of traffic lasts for hours afterwards. With a good monitoring and a good cloud vendor, the user will be aware and able to provision additional capacity within the first hour. This doesn&#039;t tackle the initial part of the spike (handled above), but does mean that many of the NYT/Digg readers will actually get a great experience when they arrive later in the day. 
    </content:encoded>

    <pubDate>Tue, 01 Jul 2008 08:05:46 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22781</guid>
    
</item>
<item>
    <title>Theo Schlossnagle: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22780</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Theo Schlossnagle)</author>
    <content:encoded>
    We use Reconnoiter to trend most of this stuff.


http://labs.omniti.com/trac/reconnoiter 
    </content:encoded>

    <pubDate>Mon, 30 Jun 2008 12:23:15 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22780</guid>
    
</item>
<item>
    <title>Peter: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22779</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Peter)</author>
    <content:encoded>
    Not about traffic spikes per se, but how are you rendering the graphs? They&#039;re pretty gorgeous &lt;img src=&quot;http://www.lethargy.org/~jesus/templates/default/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt; 
    </content:encoded>

    <pubDate>Mon, 30 Jun 2008 08:18:07 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22779</guid>
    
</item>
<item>
    <title>Andrew Binstock: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22777</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Andrew Binstock)</author>
    <content:encoded>
    The quotation about premature optimization being the root of all evil that you attribute to Knuth was actually first said by C. A. R. Hoare (see: en.wikipedia.org/wiki/C._A._R._Hoare). 

Knuth was quoting him. 
    </content:encoded>

    <pubDate>Sun, 29 Jun 2008 22:38:54 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22777</guid>
    
</item>
<item>
    <title>Chris Parente: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22776</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Chris Parente)</author>
    <content:encoded>
    Very interesting post. A couple of weeks ago there was a survey that shed some light on what carriers are doing to control spikes -- and that could affect net neutrality:

http://cparente.wordpress.com/2008/06/21/will-the-internet-break-under-peak-load/ 
    </content:encoded>

    <pubDate>Sun, 29 Jun 2008 16:37:05 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22776</guid>
    
</item>
<item>
    <title>Theo Schlossnagle: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22775</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Theo Schlossnagle)</author>
    <content:encoded>
    Well, Times was an article that included links to the site.  The article was one level off the home page (it was a section page).  So, there you see the level increase and stay increased for about 20 hours or so (with some die down due to Times traffic behaviour).

The Digg stuff, has a much shorter time frame.  It is the life of an entry on Digg on the front-page.  Anywhere from a few minutes to a few hours, but rarely longer than that. 
    </content:encoded>

    <pubDate>Sun, 29 Jun 2008 16:35:31 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22775</guid>
    
</item>
<item>
    <title>PR  NY: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22774</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (PR  NY)</author>
    <content:encoded>
    What were the events that caused those extreme spikes  (Times &amp;amp; Digg) on that graph?

Why did they  only last for only such an extreme  short period of time? 
    </content:encoded>

    <pubDate>Sun, 29 Jun 2008 10:02:53 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22774</guid>
    
</item>
<item>
    <title>Jan: Dissecting today's Internet traffic spikes</title>
    <link>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#c22773</link>
            <category></category>
    
    <comments>http://www.lethargy.org/~jesus/archives/118-Dissecting-todays-Internet-traffic-spikes.html#comments</comments>
    <wfw:comment>http://www.lethargy.org/~jesus/wfwcomment.php?cid=118</wfw:comment>

    

    <author>nospam@example.com (Jan)</author>
    <content:encoded>
    What I always find interesting is how much of the traffic &quot;sticks&quot;. We do TV advertising and have huge spikes within 3-5 seconds of the spot running. After maybe 20-30 seconds everything is back to normal again, with maybe +5-10% traffic (a normal variation). 
    </content:encoded>

    <pubDate>Mon, 23 Jun 2008 17:43:25 -0400</pubDate>
    <guid isPermaLink="false">http://www.lethargy.org/~jesus/archives/118-guid.html#c22773</guid>
    
</item>

</channel>
</rss>