<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (infovore)</title>
    <link>https://pinboard.in/u:infovore/public/</link>
    <description>recent bookmarks from infovore</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://github.com/buger/gor/"/>
	<rdf:li rdf:resource="http://lucumr.pocoo.org/2012/11/12/death-by-million-cubes/"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2012/2/13/tumblr-architecture-15-billion-page-views-a-month-and-harder.html"/>
	<rdf:li rdf:resource="http://blog.someben.com/2011/05/dreaming-of-the-cloud/"/>
	<rdf:li rdf:resource="http://pinboard.in/blog/173/"/>
	<rdf:li rdf:resource="http://axonflux.com/building-and-scaling-a-startup"/>
	<rdf:li rdf:resource="http://code.flickr.com/blog/2008/09/26/flickr-engineers-do-it-offline/"/>
	<rdf:li rdf:resource="http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html"/>
	<rdf:li rdf:resource="http://kylecordes.com/2007/07/12/youtube-scalability/"/>
	<rdf:li rdf:resource="http://blog.pmarca.com/2007/06/analyzing_the_f.html"/>
	<rdf:li rdf:resource="http://lists.danga.com/pipermail/memcached/2007-May/004098.html"/>
	<rdf:li rdf:resource="http://poorbuthappy.com/ease/archives/2007/04/29/3616/the-top-10-presentation-on-scaling-websites-twitter-flickr-bloglines-vox-and-more"/>
	<rdf:li rdf:resource="http://www.infoq.com/articles/Rails-Performance"/>
	<rdf:li rdf:resource="http://threadbox.net/articles/2005/12/15/caching-with-ruby-on-rails"/>
	<rdf:li rdf:resource="http://jeff-kubina.blogspot.com/2006/03/etech-2006-session-scaling-fast-and.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://github.com/buger/gor/">
    <title>buger/gor</title>
    <dc:date>2013-09-25T15:36:30+00:00</dc:date>
    <link>https://github.com/buger/gor/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Gor is a simple http traffic replication tool written in Go. Its main goal is to replay traffic from production servers to staging and dev environments." Handy to know about.]]></description>
<dc:subject>performance web http testing scaling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:0274da156831/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lucumr.pocoo.org/2012/11/12/death-by-million-cubes/">
    <title>Death by Million Cubes | Armin Ronacher's Thoughts and Writings</title>
    <dc:date>2013-01-17T17:02:01+00:00</dc:date>
    <link>http://lucumr.pocoo.org/2012/11/12/death-by-million-cubes/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Now that we know some of the problems, how does Curiosity solve it? The answer is: it does not. It saddens me but the game does not even appear to have realized what the problem with the design might be. The cleverness in the execution seems to stop after realizing that transmitting all the blocks at one time is a bad idea. Instead of looking at this as a form of interesting engineering problem nobody thought anything at any point..." Ouch. Great analysis of the problem, depressing analysis of the implementation. You'd really have thought game developers building a game around these very issues would have thought they'd have been critical to solve. Hey-ho.]]></description>
<dc:subject>analysis games 22cans curiosity synchronicity scaling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:36ce78bbc26c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:22cans"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:curiosity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:synchronicity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2012/2/13/tumblr-architecture-15-billion-page-views-a-month-and-harder.html">
    <title>High Scalability - High Scalability - Tumblr Architecture - 15 Billion Page Views a Month and Harder to Scale than Twitter</title>
    <dc:date>2012-02-13T20:21:51+00:00</dc:date>
    <link>http://highscalability.com/blog/2012/2/13/tumblr-architecture-15-billion-page-views-a-month-and-harder.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Really interesting post about the architecture at Tumblr, which has changed a lot over the past few years, and is a fascinating selection of tools stacked together. Especially good on the reasoning behind tool selection.]]></description>
<dc:subject>architecture scaling tumblr development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:0519033550ec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:tumblr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.someben.com/2011/05/dreaming-of-the-cloud/">
    <title>Dreaming of the Cloud | Some Ben?</title>
    <dc:date>2011-05-25T11:44:49+00:00</dc:date>
    <link>http://blog.someben.com/2011/05/dreaming-of-the-cloud/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["My dream cloud interface is not about booting virtual machines and monitoring jobs, but about spending money so my job finishes quicker. The cloud should let me launch some code, and get it chugging along in the background. Then later, I would like to spend a certain amount of money, and let reverse auction magic decide how much more CPU & RAM that money buys. This should feel like bidding for AdWords on Google. So where I might use the Unix command “nice” to prioritize a job, I could call “expensiveNice” on a PID to get that job more CPU or RAM. Virtual machines are hip this week, but applications & jobs are still the more natural way to think about computing tasks." Yes, this. And: lots of people _think_ the cloud works like this, but it really doesn't, yet. Parallelization/adding computing power is more practical, but it's not been made easy like a bunch of other things have (so far).]]></description>
<dc:subject>cloud scaling amazon ec2 parallelization justletmespendmoney</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:11a5eb126d84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:parallelization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:justletmespendmoney"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pinboard.in/blog/173/">
    <title>Anatomy of a Crushing (Pinboard Blog)</title>
    <dc:date>2011-03-09T10:29:52+00:00</dc:date>
    <link>http://pinboard.in/blog/173/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["We were a niche site and in the course of eighteen months had siphoned off about six thousand users from our massive competitor, a pace I was was very happy with and hoped to sustain through 2011. But now the Senior Vice President for Bad Decisions at Yahoo had decided to give us a little help." Maciej on what Scaling Pinboard Fast actually looked like. Some good anecdotes in here.]]></description>
<dc:subject>architecture web software performance pinboard scaling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:infovore/b:458186326c7c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:pinboard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://axonflux.com/building-and-scaling-a-startup">
    <title>Building and Scaling a Startup on Rails: 12 Things We Learned the Hard Way - Axon Flux - A Ruby on Rails Blog</title>
    <dc:date>2009-02-23T10:27:35+00:00</dc:date>
    <link>http://axonflux.com/building-and-scaling-a-startup</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Some well-worn tales here, but also some good new ones, particularly when it comes to query-profiling and all forms of caching.
]]></description>
<dc:subject>tips ruby performance development web rails scaling deployment</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:208d8c9cfc39/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:tips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.flickr.com/blog/2008/09/26/flickr-engineers-do-it-offline/">
    <title>Code: Flickr Developer Blog » Flickr Engineers Do It Offline</title>
    <dc:date>2008-09-27T14:35:25+00:00</dc:date>
    <link>http://code.flickr.com/blog/2008/09/26/flickr-engineers-do-it-offline/</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[A few notes on Flickr's queueing systems.
]]></description>
<dc:subject>flickr queue queueing development scaling scalability web programming</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:930ff962a698/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:flickr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:queue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:queueing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html">
    <title>Twitter Blog: It's Not Rocket Science, But It's Our Work</title>
    <dc:date>2008-06-02T17:54:58+00:00</dc:date>
    <link>http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[I am amazed that anyone would have the patience to respond to Mike Arrington's general arsery, but it seem the Twitter team do. They are better men and women than I.
]]></description>
<dc:subject>twitter architecture infrastructure scaling development software</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:eb0f8efb1b72/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kylecordes.com/2007/07/12/youtube-scalability/">
    <title>YouTube Scalability Talk - Kyle Cordes</title>
    <dc:date>2007-07-16T20:19:11+00:00</dc:date>
    <link>http://kylecordes.com/2007/07/12/youtube-scalability/</link>
    <dc:creator>infovore</dc:creator><dc:subject>scaling performance youtube python mysql design architecture</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:c588738ad167/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:youtube"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.pmarca.com/2007/06/analyzing_the_f.html">
    <title>blog.pmarca.com: Analyzing the Facebook Platform, three weeks in</title>
    <dc:date>2007-06-15T20:06:06+00:00</dc:date>
    <link>http://blog.pmarca.com/2007/06/analyzing_the_f.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Marc Andressen provides some interesting analysis of F8. The news for popular applications, such as iLike, isn't good.
]]></description>
<dc:subject>facebook f8 platform api web20 development scaling business</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:e8abef0858a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:f8"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:platform"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web20"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lists.danga.com/pipermail/memcached/2007-May/004098.html">
    <title>Largest production memcached install?</title>
    <dc:date>2007-05-22T20:51:13+00:00</dc:date>
    <link>http://lists.danga.com/pipermail/memcached/2007-May/004098.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA["Facebook has roughly 200 dedicated memcached servers in its production environment". Blimey. 200 x 16GB is a LOT of cache. Still, 99% of hits go straight to cache - impressive!
]]></description>
<dc:subject>facebook development memcached scaling performance caching cache</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:466dab616e32/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:memcached"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:caching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:cache"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://poorbuthappy.com/ease/archives/2007/04/29/3616/the-top-10-presentation-on-scaling-websites-twitter-flickr-bloglines-vox-and-more">
    <title>Peter Van Dijck’s Guide to Ease » Blog Archive » The top 10 presentations on scaling websites: twitter, Flickr, Bloglines, Vox and more.</title>
    <dc:date>2007-05-01T13:57:58+00:00</dc:date>
    <link>http://poorbuthappy.com/ease/archives/2007/04/29/3616/the-top-10-presentation-on-scaling-websites-twitter-flickr-bloglines-vox-and-more</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Simon is right: nice to have all this lot in one plsace.
]]></description>
<dc:subject>scaling development infrastructure presentation performance web application</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:57973c5c1b51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:presentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:application"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/articles/Rails-Performance">
    <title>InfoQ - A look at common performance problems in Rails</title>
    <dc:date>2006-06-18T09:22:55+00:00</dc:date>
    <link>http://www.infoq.com/articles/Rails-Performance</link>
    <dc:creator>infovore</dc:creator><dc:subject>performance caching ruby rubyonrails rails scaling development</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:fa2ef2494bb2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:caching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rubyonrails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://threadbox.net/articles/2005/12/15/caching-with-ruby-on-rails">
    <title>Caching with Ruby on Rails</title>
    <dc:date>2006-06-15T12:50:09+00:00</dc:date>
    <link>http://threadbox.net/articles/2005/12/15/caching-with-ruby-on-rails</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Mmn. Fragment caching. I knew I didn't want page/controller caching, was dreading this... and it all looks really rather doable. Sorted!
]]></description>
<dc:subject>caching scaling performance ruby rails rubyonrailes cache</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:1bda1e6c486e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:caching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:rubyonrailes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:cache"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jeff-kubina.blogspot.com/2006/03/etech-2006-session-scaling-fast-and.html">
    <title>vogon poetry: ETech 2006 Session: Scaling Fast and Cheap</title>
    <dc:date>2006-03-19T23:27:05+00:00</dc:date>
    <link>http://jeff-kubina.blogspot.com/2006/03/etech-2006-session-scaling-fast-and.html</link>
    <dc:creator>infovore</dc:creator><description><![CDATA[Nice write-up of Cal's tutorial
]]></description>
<dc:subject>software development scaling mysql php flickr</dc:subject>
<dc:identifier>https://pinboard.in/u:infovore/b:00333c318f50/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:infovore/t:flickr"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>