<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>My name is Alvaro and I´m currently working in Telefonica R&amp;D in Barcelona (Spain). I previously lived in Madrid, Edinburgh, Glasgow, Michigan (USA) and A Coruña (Spain).</description><title>{ inercia }</title><generator>Tumblr (3.0; @inercia)</generator><link>http://inercia.tumblr.com/</link><item><title>PacketFence: a network access control solution</title><description>&lt;a href="http://www.packetfence.org/about/overview.html"&gt;PacketFence: a network access control solution&lt;/a&gt;: &lt;p&gt;&lt;blockquote class="link_og_blockquote"&gt;&lt;span&gt;PacketFence is a fully supported, trusted, Free and Open Source network access control (NAC) solution. Boasting an impressive feature set including a captive-portal for registration and remediation, centralized wired and wireless management, 802.1X support, layer-2 isolation of problematic devices, integration with the Snort IDS and the Nessus vulnerability scanner; PacketFence can be used to effectively secure networks - from small to very large heterogeneous networks.&lt;/span&gt;&lt;/blockquote&gt;&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/50115451847</link><guid>http://inercia.tumblr.com/post/50115451847</guid><pubDate>Fri, 10 May 2013 23:55:01 +0200</pubDate><category>network access control</category><category>packetfence</category><category>security</category><category>captive-portal</category><category>wireless</category><category>snort</category></item><item><title>How do you estimate on  an Agile project?</title><description>&lt;a href="http://www.thoughtworks-studios.com/sites/default/files/resource/twebook-perspectives-estimation_1.pdf"&gt;How do you estimate on  an Agile project?&lt;/a&gt;: &lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&lt;span&gt;Estimation can be a diﬃcult beast to deal with; more so on an &lt;/span&gt;&lt;span&gt;Agile project. How do you estimate when you don’t have a list of &lt;/span&gt;&lt;span&gt;requirements that is complete or signed-oﬀ by the customer? Or &lt;/span&gt;&lt;span&gt;a nailed-down schedule? What should your currency of &lt;/span&gt;&lt;span&gt;estimation be? How do you estimate on a distributed team? Is it &lt;/span&gt;&lt;span&gt;worth estimating at all?&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;</description><link>http://inercia.tumblr.com/post/49963613122</link><guid>http://inercia.tumblr.com/post/49963613122</guid><pubDate>Thu, 09 May 2013 00:25:18 +0200</pubDate><category>agile</category><category>estimation</category></item><item><title>Dependency Inversion in practice</title><description>&lt;a href="http://martinfowler.com/articles/dipInTheWild.html"&gt;Dependency Inversion in practice&lt;/a&gt;</description><link>http://inercia.tumblr.com/post/49383115558</link><guid>http://inercia.tumblr.com/post/49383115558</guid><pubDate>Wed, 01 May 2013 22:55:47 +0200</pubDate><category>dependency inversion</category></item><item><title>Copperhead</title><description>&lt;a href="http://copperhead.github.io/"&gt;Copperhead&lt;/a&gt;: &lt;p&gt;Data parallelism brought to Python from Nvidia Research.&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/48915614893</link><guid>http://inercia.tumblr.com/post/48915614893</guid><pubDate>Fri, 26 Apr 2013 08:44:03 +0200</pubDate><category>python</category><category>nvidia</category><category>parallelism</category><category>cuda</category></item><item><title>Strategy: Using Lots of RAM Often Cheaper than Using a Hadoop Cluster</title><description>&lt;a href="http://highscalability.com/blog/2013/4/24/strategy-using-lots-of-ram-often-cheaper-than-using-a-hadoop.html"&gt;Strategy: Using Lots of RAM Often Cheaper than Using a Hadoop Cluster&lt;/a&gt;: &lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;For smaller problems memory has reached a GB/$ ratio where it is technically and financially feasible to use a single server with 100s of GB of DRAM rather than a cluster. Given the majority of analytics jobs do not process huge data sets, a cluster doesn’t need to be your first option. Scaling up RAM saves on programmer time, reduces programmer effort, improved accuracy, and reduces hardware costs.&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;</description><link>http://inercia.tumblr.com/post/48797611899</link><guid>http://inercia.tumblr.com/post/48797611899</guid><pubDate>Wed, 24 Apr 2013 23:01:58 +0200</pubDate></item><item><title>objgraph: hunting memory leaks</title><description>&lt;a href="https://pypi.python.org/pypi/objgraph"&gt;objgraph: hunting memory leaks&lt;/a&gt;</description><link>http://inercia.tumblr.com/post/46863400656</link><guid>http://inercia.tumblr.com/post/46863400656</guid><pubDate>Mon, 01 Apr 2013 20:15:04 +0200</pubDate><category>python</category><category>debugging</category><category>memory leaks</category><category>graphviz</category><category>dot</category></item><item><title>How we use Python at Spotify</title><description>&lt;a href="http://labs.spotify.com/2013/03/20/how-we-use-python-at-spotify/"&gt;How we use Python at Spotify&lt;/a&gt;</description><link>http://inercia.tumblr.com/post/45904276215</link><guid>http://inercia.tumblr.com/post/45904276215</guid><pubDate>Thu, 21 Mar 2013 10:38:22 +0100</pubDate><category>python</category><category>spotify</category><category>gevent</category><category>luigi</category></item><item><title>Redis persistence</title><description>&lt;a href="http://redis.io/topics/persistence"&gt;Redis persistence&lt;/a&gt;: &lt;p&gt;I had the idea &lt;a href="http://redis.io/" target="_blank"&gt;Redis&lt;/a&gt; did not implement &lt;em&gt;“reliable”&lt;/em&gt; persistence. I’ve always used it as a &lt;em&gt;in-memory&lt;/em&gt; key-value storage, mostly from Python. So I was looking for some persistence solutions when I found &lt;a href="http://oldblog.antirez.com/post/redis-persistence-demystified.html" target="_blank"&gt;this&lt;/a&gt; explanation by one of the developers where he tries to demystify Redis persistence.&lt;/p&gt;
&lt;p&gt;He goes on the common aspects to consider when persisting databases, explaining the interactions with the OS and why you can’t assure all data is saved to disk unless you want to do all your I/O operations synchronous (and that is something rather expensive). Then he explains the main persistence alternatives: snapshottings and AOF files.&lt;/p&gt;
&lt;p&gt;Snapshots just dump the whole dataset to a disk image, but they are expensive operations and cannot be performed too often (they are usually done every 5 minutes or so). In contrast, AOF files do little I/O by saving to a file all the operations as they happen, right in the same order as they are executed by the server, so they can be replayed in case of a crash. In my view, and &lt;span&gt;depending on the &lt;em&gt;fsync&lt;/em&gt; policy you use (that forces a commit of data to disk), &lt;/span&gt;&lt;span&gt;AOF files can provide the same reliability as any other &lt;/span&gt;&lt;em&gt;conventional&lt;/em&gt;&lt;span&gt; database (ie, PostgreSQL). And, as the author explains, both methods can be combined for increased security: &lt;/span&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;From a more practical point of view Redis provides both AOF and RDB snapshots, that can be enabled simultaneously (this is the advised setup, when in doubt), offering at the same time easy of operations and data durability. &lt;/p&gt;
&lt;/blockquote&gt;</description><link>http://inercia.tumblr.com/post/45831780594</link><guid>http://inercia.tumblr.com/post/45831780594</guid><pubDate>Wed, 20 Mar 2013 13:47:00 +0100</pubDate><category>Redis</category><category>persistence</category><category>databases</category><category>nosql</category></item><item><title>Async I/O for Python 3</title><description>&lt;a href="https://www.dropbox.com/s/xknbe58zcvjhzhv/PyCon2013.pptx"&gt;Async I/O for Python 3&lt;/a&gt;: &lt;p&gt;A presentation by Guido van Rossum on h&lt;span&gt;&lt;/span&gt;&lt;span&gt;ow &lt;/span&gt;&lt;a href="http://www.python.org/dev/peps/pep-3156/" target="_blank"&gt;Tulip&lt;/a&gt;&lt;span&gt; is going to replace &lt;/span&gt;&lt;a href="http://www.gevent.org/" target="_blank"&gt;gevent&lt;/a&gt;&lt;span&gt;, &lt;/span&gt;&lt;a href="http://www.tornadoweb.org/en/stable/" target="_blank"&gt;Tornado&lt;/a&gt;&lt;span&gt; and all those incompatible libraries…&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="" src="https://proxy.docs.dropboxdocs.com/HztoGjfKwHBk30jbsJ335p9aTglj_7lgLU4BZ5SruD4ga34U7_dyHW_fDEXF4GGkFs9roK7-CksHmyVzC8y_fGlEGRWdMAOOep63P0UOu_FAUSoQALfNZNIJbUp3TdTcR2xA0MXtCaCoXPfHhtJvUqwypuTG-S-yca1oW6QHZUzxeU0HM-D5RZ3w5rMdlCaarvAjaVBCvbFBRNsCL0Ja3LDXBPCheRERMKyT94zzA2dWiert0Zw7d_0m1DBd3J4V2tJsu5s6AX50jDGpsAxyq9XrM83M7kZaSTYnkA/8qLkbrjAUtDGc2Z5v7OwXUJpyWvMCgXKjJjGjAYb2IrhIDwh5sVgz6E6MZoIwoe9USwy0BytcnQ9lMUELdRXIoN-vviM-GUslLw8Uw/images/page-43.png"/&gt;&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/45761840003</link><guid>http://inercia.tumblr.com/post/45761840003</guid><pubDate>Tue, 19 Mar 2013 17:34:58 +0100</pubDate><category>python</category><category>tulip</category><category>asynchronous</category><category>networking</category></item><item><title>Using Redis as LINE storage</title><description>&lt;a href="http://tech.naver.jp/blog/?p=1420"&gt;Using Redis as LINE storage&lt;/a&gt;: &lt;p&gt;How they used &lt;a href="http://redis.io/" target="_blank"&gt;Redis&lt;/a&gt; as storage in &lt;a href="http://line.naver.jp/en/" target="_blank"&gt;LINE&lt;/a&gt;, and how they scaled up with the help of Hadoop, &lt;a href="http://hbase.apache.org/" target="_blank"&gt;HBase&lt;/a&gt; and some other tools…&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/45708225191</link><guid>http://inercia.tumblr.com/post/45708225191</guid><pubDate>Tue, 19 Mar 2013 00:06:00 +0100</pubDate><category>Redis</category><category>scalability</category><category>LINE</category><category>storage</category><category>hadoop</category><category>hbase</category></item><item><title>Nginx &amp; WebSockets</title><description>&lt;a href="http://nginx.org/en/docs/http/websocket.html"&gt;Nginx &amp; WebSockets&lt;/a&gt;: &lt;p&gt;There is WebSockets support in Nginx since versión 1.3.13. See how to use it &lt;a href="https://chrislea.com/2013/02/23/proxying-websockets-with-nginx/" target="_blank"&gt;here&lt;/a&gt;&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/45377849339</link><guid>http://inercia.tumblr.com/post/45377849339</guid><pubDate>Fri, 15 Mar 2013 00:32:27 +0100</pubDate></item><item><title>Plop: Python Profiler With Call Graphs</title><description>&lt;a href="http://emptysquare.net/blog/plop-python-profiler-with-call-graphs"&gt;Plop: Python Profiler With Call Graphs&lt;/a&gt;: &lt;p&gt;A new profiler for Python…&lt;/p&gt;

&lt;p&gt;&lt;img alt="" src="http://emptysquare.net/blog/media/2013/03/call-graph.png"/&gt;&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/45263861933</link><guid>http://inercia.tumblr.com/post/45263861933</guid><pubDate>Wed, 13 Mar 2013 13:33:53 +0100</pubDate><category>python</category><category>Profiling</category><category>performance</category></item><item><title>Under the Hood: Building out the infrastructure for Graph Search</title><description>&lt;a href="https://www.facebook.com/notes/facebook-engineering/under-the-hood-building-out-the-infrastructure-for-graph-search/10151347573598920"&gt;Under the Hood: Building out the infrastructure for Graph Search&lt;/a&gt;</description><link>http://inercia.tumblr.com/post/44777979585</link><guid>http://inercia.tumblr.com/post/44777979585</guid><pubDate>Thu, 07 Mar 2013 12:12:34 +0100</pubDate><category>facebook</category><category>software architecture</category></item><item><title>Why Intel can't seem to retire the x86</title><description>&lt;a href="http://www.itworld.com/print/346559"&gt;Why Intel can't seem to retire the x86&lt;/a&gt;: &lt;blockquote&gt;
&lt;p&gt;&lt;span&gt;The x86 microarchitecture is another aged technology, and it has survived more assassination attempts than Fidel Castro. What makes the number of attempts on x86 more interesting is that Intel is the one who keeps trying to take it out.&lt;/span&gt;&lt;/p&gt;
&lt;/blockquote&gt;</description><link>http://inercia.tumblr.com/post/44710481643</link><guid>http://inercia.tumblr.com/post/44710481643</guid><pubDate>Wed, 06 Mar 2013 17:09:51 +0100</pubDate><category>intel</category><category>x86</category><category>hardware architecture</category></item><item><title>The BitTorrent Engineering blog</title><description>&lt;a href="http://engineering.bittorrent.com/"&gt;The BitTorrent Engineering blog&lt;/a&gt;: &lt;p&gt;They have recently opened the blog so there is not much content yet, but I’ve found two interesting articles:&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a href="http://engineering.bittorrent.com/2013/02/04/udp-multicast-in-python-and-bittorrent-live/" target="_blank"&gt;UDP Multicast in Python and BitTorrent Live&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://engineering.bittorrent.com/2013/01/22/bittorrent-tech-talks-dht/" target="_blank"&gt;BitTorrent Tech Talks: DHT&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description><link>http://inercia.tumblr.com/post/44611334247</link><guid>http://inercia.tumblr.com/post/44611334247</guid><pubDate>Tue, 05 Mar 2013 11:03:39 +0100</pubDate><category>BitTorrent</category><category>DHT</category><category>python</category><category>multicast</category><category>udp</category></item><item><title>Thialﬁ: A Client Notiﬁcation Service for Internet-Scale Applications</title><description>&lt;a href="http://www.michaelpiatek.com/papers/thialfi-sosp11.pdf"&gt;Thialﬁ: A Client Notiﬁcation Service for Internet-Scale Applications&lt;/a&gt;: &lt;p&gt;A paper on Thialfi, the framework used at Google for notifications. They claim they can scale to millions of users, and with a delay of less than a second…&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/44210118190</link><guid>http://inercia.tumblr.com/post/44210118190</guid><pubDate>Thu, 28 Feb 2013 10:43:39 +0100</pubDate><category>distributed systems</category><category>scalability</category><category>performance</category><category>messaging</category></item><item><title>The purpose of estimations</title><description>&lt;a href="http://martinfowler.com/bliki/PurposeOfEstimation.html"&gt;The purpose of estimations&lt;/a&gt;</description><link>http://inercia.tumblr.com/post/44151107491</link><guid>http://inercia.tumblr.com/post/44151107491</guid><pubDate>Wed, 27 Feb 2013 19:15:34 +0100</pubDate></item><item><title>Python Profiling tools</title><description>&lt;a href="http://www.logilab.org/blogentry/104898"&gt;Python Profiling tools&lt;/a&gt;</description><link>http://inercia.tumblr.com/post/44056766268</link><guid>http://inercia.tumblr.com/post/44056766268</guid><pubDate>Tue, 26 Feb 2013 12:23:12 +0100</pubDate><category>python</category><category>profiling</category></item><item><title>Vitess</title><description>&lt;a href="http://code.google.com/p/vitess/"&gt;Vitess&lt;/a&gt;: &lt;p&gt;A scalable RPC interface to MySQL, with client-side sharding, limited ACID support and more&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/43885598510</link><guid>http://inercia.tumblr.com/post/43885598510</guid><pubDate>Sun, 24 Feb 2013 12:51:29 +0100</pubDate><category>mysql</category><category>python</category><category>scalability</category></item><item><title>Pypy vs Gevent vs Node.Js</title><description>&lt;a href="http://blog.kgriffs.com/2012/11/13/python-vs-node-vs-pypy-benchmarks.html"&gt;Pypy vs Gevent vs Node.Js&lt;/a&gt;: &lt;p&gt;A new comparison on the performance of Python and Node.JS. As we could expect, Node outperforms Python in terms of latency, specially for short connections, but, for big data transfers, there is a negligible difference between both languages…&lt;/p&gt;</description><link>http://inercia.tumblr.com/post/43520293841</link><guid>http://inercia.tumblr.com/post/43520293841</guid><pubDate>Wed, 20 Feb 2013 00:38:39 +0100</pubDate><category>python</category><category>pypy</category><category>nodejs</category><category>node</category><category>javascript</category><category>gevent</category><category>performance</category><category>networking</category></item></channel></rss>
