<?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 (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://zeynep.substack.com/p/the-gaslighting-of-science"/>
	<rdf:li rdf:resource="https://www.mhlw.go.jp/content/10900000/000635891.pdf"/>
	<rdf:li rdf:resource="https://blog.google/inside-google/infrastructure/data-centers-work-harder-sun-shines-wind-blows"/>
	<rdf:li rdf:resource="https://medium.com/@ranshn/the-definitive-guide-to-running-ec2-spot-instances-as-kubernetes-worker-nodes-68ef2095e767"/>
	<rdf:li rdf:resource="https://medium.com/aws-activate-startup-blog/cluster-based-architectures-using-docker-and-amazon-ec2-container-service-f74fa86254bf"/>
	<rdf:li rdf:resource="http://www.infoq.com/news/2014/04/hydra"/>
	<rdf:li rdf:resource="http://www.serfdom.io/intro/index.html"/>
	<rdf:li rdf:resource="http://yahooeng.tumblr.com/post/64758709722/making-storm-fly-with-netty"/>
	<rdf:li rdf:resource="https://github.com/infochimps-labs/ironfan/wiki/walkthrough-web"/>
	<rdf:li rdf:resource="http://petewarden.typepad.com/searchbrowser/2010/02/how-to-split-up-the-us.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://zeynep.substack.com/p/the-gaslighting-of-science">
    <title>The Gaslighting of Science - Insight</title>
    <dc:date>2021-04-11T21:18:02+00:00</dc:date>
    <link>https://zeynep.substack.com/p/the-gaslighting-of-science</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Zeynep Tufekci hits the nail on the head here -- 3 particular factors were wilfully overlooked in Western countries' early response to the COVID pandemic:

<blockquote>Put all three together: airborne transmission, clusters driving the epidemic, and presymptomatic transmission. Not only do we get a clear and consistent picture of many things that have happened since, we also get the mitigation strategy. Further, all three dimensions support each other: transmission from people not (yet) coughing or sneezing very much argues in favor of aerosol transmission, which explains how large clusters can be driving the epidemic and how transmission in a situation like that ship can occur. And the mitigation and other strategies become clear: pay attention to clusters and ventilation, universal masks, different policies for indoors and outdoors, etc. </blockquote>

]]></description>
<dc:subject>zeynep-tufekci coronavirus science covid-19 aerosols transmission clusters</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:697b6ca481c2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:zeynep-tufekci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coronavirus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:covid-19"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aerosols"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transmission"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.mhlw.go.jp/content/10900000/000635891.pdf">
    <title>Japan's approach to combat COVID-19 [pdf]</title>
    <dc:date>2020-06-03T21:18:24+00:00</dc:date>
    <link>https://www.mhlw.go.jp/content/10900000/000635891.pdf</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Very interesting and detailed presentation, particularly the info about how they perform retrospective contact tracing to narrow down the sources of community transmission and monitor other contacts, who may be asymptomatic but still infectious.]]></description>
<dc:subject>covid-19 japan pandemics contact-tracing clusters infection</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:81d4ef4613b9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:covid-19"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:japan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pandemics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:contact-tracing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infection"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.google/inside-google/infrastructure/data-centers-work-harder-sun-shines-wind-blows">
    <title>Google's data centers now work harder when the sun shines and wind blows</title>
    <dc:date>2020-04-23T10:48:55+00:00</dc:date>
    <link>https://blog.google/inside-google/infrastructure/data-centers-work-harder-sun-shines-wind-blows</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is fantastic -- aligning batch processing jobs to the availability of sustainable energy:

<blockquote>Our latest advancement in sustainability, developed by a small team of engineers, is a new carbon-intelligent computing platform. We designed and deployed this first-of-its kind system for our hyperscale (meaning very large) data centers to shift the timing of many compute tasks to when low-carbon power sources, like wind and solar, are most plentiful. This is done without additional computer hardware and without impacting the performance of Google services like Search, Maps and YouTube that people rely on around the clock. Shifting the timing of non-urgent compute tasks—like creating new filter features on Google Photos, YouTube video processing, or adding new words to Google Translate—helps reduce the electrical grid’s carbon footprint, getting us closer to 24x7 carbon-free energy.</blockquote>

]]></description>
<dc:subject>energy google sustainability green clusters datacenters power</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c82fd1e31d0c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:energy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sustainability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:green"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:datacenters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:power"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@ranshn/the-definitive-guide-to-running-ec2-spot-instances-as-kubernetes-worker-nodes-68ef2095e767">
    <title>The definitive guide to running EC2 Spot Instances as Kubernetes worker nodes</title>
    <dc:date>2019-05-22T10:46:45+00:00</dc:date>
    <link>https://medium.com/@ranshn/the-definitive-guide-to-running-ec2-spot-instances-as-kubernetes-worker-nodes-68ef2095e767</link>
    <dc:creator>jm</dc:creator><description><![CDATA[it really is quite definitive, good writeup]]></description>
<dc:subject>ec2 spot-instances cost-saving kubernetes clusters asg aws</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6f043fb3a3f0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spot-instances"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cost-saving"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:asg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/aws-activate-startup-blog/cluster-based-architectures-using-docker-and-amazon-ec2-container-service-f74fa86254bf">
    <title>Cluster-Based Architectures Using Docker and Amazon EC2 Container Service</title>
    <dc:date>2015-04-24T13:56:08+00:00</dc:date>
    <link>https://medium.com/aws-activate-startup-blog/cluster-based-architectures-using-docker-and-amazon-ec2-container-service-f74fa86254bf</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>In this post, we’re going to take a deeper dive into the architectural concepts underlying cluster computing using container management frameworks such as ECS. We will show how these frameworks effectively abstract the low-level resources such as CPU, memory, and storage, allowing for highly efficient usage of the nodes in a compute cluster. Building on some of the concepts detailed in the earlier posts, we will discover why containers are such a good fit for this type of abstraction, and how the Amazon EC2 Container Service fits into the larger ecosystem of cluster management frameworks.</blockquote>

]]></description>
<dc:subject>docker aws ecs ec2 ops hosting containers mesos clusters</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:5c48004c7952/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:docker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ecs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:containers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mesos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/news/2014/04/hydra">
    <title>Hydra Takes On Hadoop</title>
    <dc:date>2014-04-15T09:03:04+00:00</dc:date>
    <link>http://www.infoq.com/news/2014/04/hydra</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>The intuition behind Hydra is something like this, "I have a lot of data, and there are a lot of things I could try to learn about it -- so many that I'm not even sure what I want to know.” It's about the curse of dimensionality -- more dimensions means exponentially more cost for exhaustive analysis. Hydra tries to make it easy to reduce the number of dimensions, or the cost of watching them (via probabilistic data structures), to just the right point where everything runs quickly but can still answer almost any question you think you might care about.</blockquote>

Code: https://github.com/addthis/hydra

Getting Started blog post: https://www.addthis.com/blog/2014/02/18/getting-started-with-hydra/
]]></description>
<dc:subject>hyrda hadoop data-processing big-data trees clusters analysis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:88e7ba130d36/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hyrda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data-processing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:big-data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trees"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analysis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.serfdom.io/intro/index.html">
    <title>Serf</title>
    <dc:date>2013-11-01T16:52:34+00:00</dc:date>
    <link>http://www.serfdom.io/intro/index.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA['a service discovery and orchestration tool that is decentralized, highly available, and fault tolerant. Serf runs on every major platform: Linux, Mac OS X, and Windows. It is extremely lightweight: it uses 5 to 10 MB of resident memory and primarily communicates using infrequent UDP messages [and an] efficient gossip protocol.']]></description>
<dc:subject>clustering service-discovery ops linux gossip broadcast clusters</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:33c38925937b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clustering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:service-discovery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gossip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:broadcast"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://yahooeng.tumblr.com/post/64758709722/making-storm-fly-with-netty">
    <title>Making Storm fly with Netty | Yahoo Engineering</title>
    <dc:date>2013-10-23T21:09:21+00:00</dc:date>
    <link>http://yahooeng.tumblr.com/post/64758709722/making-storm-fly-with-netty</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Y! engineer doubles the speed of Storm's messaging layer by replacing the zeromq implementation with Netty]]></description>
<dc:subject>netty async zeromq storm messaging tcp benchmarks yahoo clusters</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:0980d14db16f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:async"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:zeromq"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tcp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:benchmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:yahoo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/infochimps-labs/ironfan/wiki/walkthrough-web">
    <title>Ironfan</title>
    <dc:date>2013-01-27T21:11:16+00:00</dc:date>
    <link>https://github.com/infochimps-labs/ironfan/wiki/walkthrough-web</link>
    <dc:creator>jm</dc:creator><description><![CDATA['an expressive toolset for constructing scalable, resilient [service] architectures. It works in the cloud, in the data center, and on your laptop, and it makes your system diagram visible and inevitable. Inevitable systems coordinate automatically to interconnect, removing the hassle of manual configuration of connection points (and the associated danger of human error).'  Looks like a pretty neat cluster deployment tool; driven from a single configuration file, using Chef, integrating closely with AWS and providing many useful additional features]]></description>
<dc:subject>chef deployment clusters knife services aws ec2 ops ironfan demo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ed73e23aae92/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:knife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ironfan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:demo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://petewarden.typepad.com/searchbrowser/2010/02/how-to-split-up-the-us.html">
    <title>PeteSearch: How to split up the US</title>
    <dc:date>2010-02-08T15:25:42+00:00</dc:date>
    <link>http://petewarden.typepad.com/searchbrowser/2010/02/how-to-split-up-the-us.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[wow.  fascinating results from social-network cluster analysis of Facebook, splitting up the entire USA into 7 clusters]]></description>
<dc:subject>clusters facebook data statistics maps culture analytics datamining demographics socialnetworking graph dataviz</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:11f5af518b1b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:datamining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:demographics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:socialnetworking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:graph"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dataviz"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>