<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Adam's Rants &amp; Ramblings</title><link>https://comerford.net/post/</link><description>Recent content in Posts on Adam's Rants &amp; Ramblings</description><image><title>Adam's Rants &amp; Ramblings</title><url>https://comerford.net/images/dublin.jpg</url><link>https://comerford.net/images/dublin.jpg</link></image><generator>Hugo</generator><language>en-GB</language><copyright>Adam Comerford</copyright><lastBuildDate>Mon, 14 Apr 2025 00:00:00 +0100</lastBuildDate><atom:link href="https://comerford.net/post/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a WiFi Router from (mostly) Spare Parts</title><link>https://comerford.net/2025/04/14/building-wifi-router/</link><pubDate>Mon, 14 Apr 2025 00:00:00 +0100</pubDate><guid>https://comerford.net/2025/04/14/building-wifi-router/</guid><description>&lt;p&gt;Some time ago, I set about building my own wireless router.&lt;/p&gt;
&lt;p&gt;Why?&lt;/p&gt;
&lt;p&gt;Well, I wanted to see if I could put something together that would (theoretically) be upgradeable rather than disposable once standards moved on. I also had an existing setup (Unifi DreamRouter from their defunct early access program) that could not do the latest speeds, was limited to 1Gbit, and would be a good fit for upgrading my parent&amp;rsquo;s home set up. Finally, I had a collection of spare parts and no real purpose to put them to - this seemed like a good fit. Up front I should say that even with these spare parts, this is not a cost effective way to create a router - you will not be saving money here. In my case, because I am reusing an old mid-tower case it also won&amp;rsquo;t be particularly compact or power efficient. It was a lot of fun though, so from that perspective it was mission accomplished. I will get into how it performs, how I update it and configure it later, but this post will focus on the hardware, putting it together, what it cost etc.&lt;/p&gt;</description></item><item><title>Sharing Failures - Interviewing is Hard</title><link>https://comerford.net/2020/06/16/sharing-failures-interviewing-is-hard/</link><pubDate>Tue, 16 Jun 2020 00:00:00 +0100</pubDate><guid>https://comerford.net/2020/06/16/sharing-failures-interviewing-is-hard/</guid><description>&lt;p&gt;I will get to part 3 of my series on becoming an engineer again, but that needs some more time to bake (&lt;a href="https://comerford.net/2020/05/15/swinging-the-pendulum-becoming-an-engineer-again/"&gt;part 1&lt;/a&gt; and &lt;a href="https://comerford.net/2020/05/17/becoming-an-engineer-again-fog-and-rust/"&gt;part 2&lt;/a&gt; for those interested). In the meantime, something a little different&amp;hellip;&lt;/p&gt;
&lt;p&gt;This is one of those posts that was difficult to write, and once written it was difficult to publish - it’s not easy to talk about failure. When I see how people react to such posts from others, in addition to just how demoralised and depressed people can get when they don’t get their dream job, deciding to share myself was made a lot easier.&lt;/p&gt;</description></item><item><title>Becoming an Engineer Again - Fog and Rust</title><link>https://comerford.net/2020/05/17/becoming-an-engineer-again-fog-and-rust/</link><pubDate>Sun, 17 May 2020 00:00:00 +0100</pubDate><guid>https://comerford.net/2020/05/17/becoming-an-engineer-again-fog-and-rust/</guid><description>&lt;p&gt;Although my &lt;a href="https://comerford.net/2020/05/15/swinging-the-pendulum-becoming-an-engineer-again/"&gt;first post&lt;/a&gt; on this topic stated that a mindset shift was the key to a successful transition, it also takes some time to achieve. It is a longer term goal that I am working towards, but I don’t expect to make it happen in a couple of weeks. So, while there may be a post about approach and progress in that category relatively soon, it needs some time to bake.&lt;/p&gt;</description></item><item><title>Swinging the Pendulum - Becoming an Engineer Again</title><link>https://comerford.net/2020/05/15/swinging-the-pendulum-becoming-an-engineer-again/</link><pubDate>Fri, 15 May 2020 00:00:00 +0100</pubDate><guid>https://comerford.net/2020/05/15/swinging-the-pendulum-becoming-an-engineer-again/</guid><description>&lt;p&gt;The &lt;a href="https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/"&gt;pendulum&lt;/a&gt; is swinging again, and it is swinging a lot faster this time than it has previously. I asked &lt;a href="https://twitter.com/comerford/status/1259120458798174209"&gt;on Twitter&lt;/a&gt; whether people would be interested in some posts as I work through this change and the answer was yes. So here we are&amp;hellip;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Not My First Rodeo&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;First things first - I like to remind myself that I have done this before, though a lot less deliberately. While working at MongoDB I was a manager for 2 years, eventually burned out in that role, and then made the shift back to engineering work (Solutions Engineering, then Consulting Engineering). The most obvious difference that time around was that I made the shift while staying in the same company.&lt;/p&gt;</description></item><item><title>Deploying Secure Asset Distribution with AWS and Terraform</title><link>https://comerford.net/2016/05/09/deploying-secure-asset-distribution-with-aws-terraform/</link><pubDate>Mon, 09 May 2016 00:00:00 +0100</pubDate><guid>https://comerford.net/2016/05/09/deploying-secure-asset-distribution-with-aws-terraform/</guid><description>&lt;p&gt;I was recently asked to come up with a solution for hosting some media files for a site. The requirements were pretty straight forward:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Should be available via &lt;a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol"&gt;HTTP&lt;/a&gt; and &lt;a href="https://en.wikipedia.org/wiki/HTTPS"&gt;HTTPS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Minimal support requirements&lt;/li&gt;
&lt;li&gt;&lt;a href="https://en.wikipedia.org/wiki/Amazon_Web_Services"&gt;AWS&lt;/a&gt; Based&lt;/li&gt;
&lt;li&gt;Assets can be uploaded to the hosting with minimal effort/knowledge&lt;/li&gt;
&lt;li&gt;Site should be performant within Europe (in particular)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The rest of the post will detail why I chose the solution I did to satisfy those requirements and how I went about configuring it. It includes a generalised version of the configuration in Github and even a diagram to illustrate!&lt;/p&gt;</description></item><item><title>Switching to Hugo from Wordpress</title><link>https://comerford.net/2016/02/29/switching-to-hugo-from-wordpress/</link><pubDate>Mon, 29 Feb 2016 00:00:00 +0000</pubDate><guid>https://comerford.net/2016/02/29/switching-to-hugo-from-wordpress/</guid><description>&lt;p&gt;Something I have been meaning to do for a while is to switch away from Wordpress. While it is quite a nice collaborative tool and has some great options for WYSIWIG editing and content, it&amp;rsquo;s also far too big a hammer to use given my modest content and collaboration needs. I don&amp;rsquo;t have guest posters, I don&amp;rsquo;t get a lot of comments, and when I do get some interactions they would often work better in another medium (&lt;a href="https://twitter.com/comerford"&gt;Twitter&lt;/a&gt; for example). I don&amp;rsquo;t have a lot of dynamic content and running Wordpress myself is not something I am particularly expert in.&lt;/p&gt;
&lt;p&gt;I had been considering several options, but when I saw Steve&amp;rsquo;s work with &lt;a href="https://gohugo.io"&gt;Hugo&lt;/a&gt; I was sold (this was early days in the project and it was still pretty awesome). The big stumbling block was what to do with my old content and that stalled me out for a while. Around the same time as I contemplated the switch, I finally obtained the comerford.net domain - I had watched it for some time while someone sat on it, not using it, for years. I even tried making an offer for it (at what I considered a reasonable price) but got nothing, so I decided to wait for it to expire, which it eventually did.&lt;/p&gt;</description></item><item><title>Reflecting on 3 Years at MongoDB</title><link>https://comerford.net/2015/03/10/reflecting-on-3-years-at-mongodb/</link><pubDate>Tue, 10 Mar 2015 00:00:00 +0000</pubDate><guid>https://comerford.net/2015/03/10/reflecting-on-3-years-at-mongodb/</guid><description>&lt;p&gt;This post took a while to write – when I started, it was my last day in &lt;a href="http://www.mongodb.com/" target="_blank"&gt;MongoDB&lt;/a&gt; and finishing it I am over a week into my new role in &lt;a href="http://www.riotgames.com/" target="_blank"&gt;Riot Games&lt;/a&gt;.  It was a bittersweet moment – I was very excited to move on to my new adventure in Riot Games, but I was sad to leave a company that has been such a great place to work for the last three years.  I decided to write this post partially as a record of what I enjoyed most, partly as a list of some of my accomplishments – memory fades and I have very much enjoyed reading similar posts from several years ago.  I often wish I had written more in fact.&lt;/p&gt;
&lt;p&gt;So, here it is, some random reflection on three great years, in no particular order.  Due to the length, I’ll insert a jump, so click through if you would like to read on.&lt;/p&gt;</description></item><item><title>Explaining Parenting in Gaming Terminology</title><link>https://comerford.net/2015/03/02/explaining-parenting-in-gaming-terminology/</link><pubDate>Mon, 02 Mar 2015 00:00:00 +0000</pubDate><guid>https://comerford.net/2015/03/02/explaining-parenting-in-gaming-terminology/</guid><description>&lt;p&gt;I was asked to do an “About Me” introduction for my &lt;a href="http://www.riotgames.com/" target="_blank"&gt;new gig&lt;/a&gt;, and wasn’t sure how to mention the fact that I had recently become a parent for the first time.  Given the fact that I now work for a games company, I decided to have a bit of fun with it and translate it into more gamer-friendly format. I think it turned out pretty well:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I’ve just started playing a new game called Parenting, it’s in early beta, only at version 0.5 (first released in August 2014). It’s a co-op game with solo parts, usually much easier with 2 players (so I usually team up with my wife) but you can occasionally use other people to form larger parties for short periods of time. It’s a massive time sink and the learning curve is brutal, but very rewarding and not a little addictive.&lt;/p&gt;
&lt;p&gt;The opposing AI in Parenting is developing rapidly and new strategies are required constantly to combat the adaptation and avoiding meltdown. Right now, the game requires constant attention, even at night, it’s expensive and there are no save points – it’s a little scary. The progression is not slowing down either, and looks to be open ended, will probably take decades to complete but we will persevere 🙂&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>MongoDB 3.0: Hitting 1.3 Million Inserts/Sec with mongorestore</title><link>https://comerford.net/2015/02/12/mongodb-3-0-hitting-1-3-million-insertssec-with-mongorestore/</link><pubDate>Thu, 12 Feb 2015 00:00:00 +0000</pubDate><guid>https://comerford.net/2015/02/12/mongodb-3-0-hitting-1-3-million-insertssec-with-mongorestore/</guid><description>&lt;p&gt;This will likely be my last post about MongoDB 3.0 performance, as I am leaving MongoDB (after 3 fantastic years) to join Riot Games – more about that in later posts. Before I go, some testing I was doing to verify WiredTiger performance with the journal disabled led to some eye-catching numbers.  While performing a restore using 3.0 mongorestore to a 3.0 mongod with 4 collections, I noticed I was pushing close to 300,000 inserts/sec.&lt;/p&gt;</description></item><item><title>MongoDB 3.0: Benefits of Compression with Limited IO</title><link>https://comerford.net/2015/02/05/mongodb-3-0-benefits-of-compression-with-limited-io/</link><pubDate>Thu, 05 Feb 2015 00:00:00 +0000</pubDate><guid>https://comerford.net/2015/02/05/mongodb-3-0-benefits-of-compression-with-limited-io/</guid><description>&lt;p&gt;I re-ran my compression testing from November to show the on-disk savings that compression in WiredTiger allows in my &lt;a href="https://comerford.net/2015/02/04/mongodb-3-0-testing-compression/" target="_blank"&gt;last post&lt;/a&gt;.  The other part of that testing was to see if we could show a benefit to having compressed data from a read perspective.  As I &lt;a href="https://comerford.net/2014/11/12/mongodb-2-8-new-wiredtiger-storage-engine-adds-compression/" target="_blank"&gt;explained back in November&lt;/a&gt;, one of the scenarios where compression can help is when there is only limited IO capacity available.&lt;/p&gt;
&lt;p&gt;Once again, to simulate that, I used a relatively slow external USB 3.0 drive to simulate reasonable IO constraints and then recorded how long it took to read my entire data set from the on-disk testing into memory from that disk. The results show that benefit, though the results in WiredTiger are somewhat hampered by the issue described in &lt;a href="https://jira.mongodb.org/browse/SERVER-16444" target="_blank"&gt;SERVER-16444&lt;/a&gt;. I may attempt to re-run these tests with a more random, index driven read load – as well as being more representative of a normal workload, it should also show greater benefits by avoiding the table scan related overheads.&lt;/p&gt;</description></item><item><title>MongoDB 3.0: Testing Compression</title><link>https://comerford.net/2015/02/04/mongodb-3-0-testing-compression/</link><pubDate>Wed, 04 Feb 2015 00:00:00 +0000</pubDate><guid>https://comerford.net/2015/02/04/mongodb-3-0-testing-compression/</guid><description>&lt;p&gt;Back in November, with the newly minted RC0 version of MongoDB 3.0 (then 2.8 of course), I ran &lt;a href="https://comerford.net/2014/11/12/mongodb-2-8-new-wiredtiger-storage-engine-adds-compression/" target="_blank"&gt;a series of tests&lt;/a&gt; to check out how well compression using the new WiredTiger storage engine worked with a ~16GB data sample.  Compression on disk worked fine, but the follow up tests to show the benefits of using compression when limited IO is available ran into issues and I ended up having to &lt;a href="https://comerford.net/2014/11/17/mongodb-2-8-improving-wiredtiger-performance/" target="_blank"&gt;run the tests again&lt;/a&gt; with an updated version (and the appropriate bug fix).&lt;/p&gt;</description></item><item><title>MongoDB 2.8: Improving WiredTiger Performance</title><link>https://comerford.net/2014/11/17/mongodb-2-8-improving-wiredtiger-performance/</link><pubDate>Mon, 17 Nov 2014 00:00:00 +0000</pubDate><guid>https://comerford.net/2014/11/17/mongodb-2-8-improving-wiredtiger-performance/</guid><description>&lt;p&gt;My (rather popular) &lt;a href="https://comerford.net/2014/11/12/mongodb-2-8-new-wiredtiger-storage-engine-adds-compression/" target="_blank"&gt;first post&lt;/a&gt; on this topic explained the benefits of compression (which comes as the default option with the new WiredTiger storage engine) for systems with lesser IO capabilities.  The intent was to first show that the new storage engine saved space on disk and then to show that this could be translated into a gain in terms of performance when reading that data (slowly) off disk.&lt;/p&gt;
&lt;p&gt;The first part of that story worked out pretty well, the data was nicely compressed on disk and it was easy to show it in the graph.  The second part of that story did not work out as expected, &lt;a href="https://comerford.net/img/legacy/images/ttld_compression.png" target="_blank"&gt;the graph&lt;/a&gt; was a little off from expectations and my initial speculation that it was a non-optimal access pattern didn’t pan out.  In fact, I determined that the slowness I was seeing was independent of IO and was due to how slow the in-memory piece was when using WiredTiger to do a table scan.  Needless to say, I started to talk to engineering about the issue and tried tweaking various options – each one essentially reinforced the original finding.&lt;/p&gt;
&lt;p&gt;It was soon obvious that we had a bug that needed to be addressed (one that was still present in the &lt;a href="http://blog.mongodb.org/post/102461818738/announcing-mongodb-2-8-0-rc0-release-candidate-and-bug" target="_blank"&gt;first release candidate 2.8.0-rc0&lt;/a&gt;). I gathered the relevant data and &lt;a href="https://jira.mongodb.org/browse/SERVER-16150" target="_blank"&gt;opened SERVER-16150&lt;/a&gt; to investigate the problem. Thanks to the ever excellent folks in MongoDB engineering (&lt;a href="https://github.com/RedBeard0531" target="_blank"&gt;this one&lt;/a&gt; in particular), we soon had the first patched build attempting to address the issue (more, with graphs after the jump).  Before that, for anyone looking to reproduce this testing, I would recommend waiting until SERVER-16150 has been closed and integrated into the next release candidate (2.8.0-rc1), you won’t see the same results from 2.8.0-rc0 (it will instead look like the first set of results).&lt;/p&gt;</description></item><item><title>MongoDB 2.8 – New WiredTiger Storage Engine Adds Compression</title><link>https://comerford.net/2014/11/12/mongodb-2-8-new-wiredtiger-storage-engine-adds-compression/</link><pubDate>Wed, 12 Nov 2014 00:00:00 +0000</pubDate><guid>https://comerford.net/2014/11/12/mongodb-2-8-new-wiredtiger-storage-engine-adds-compression/</guid><description>&lt;p&gt;&lt;strong&gt;CAVEAT: This post deals with a development version of MongoDB and represents very early testing. The version used was not even a release candidate – 2.7.9-pre to be specific, this is not even a release candidate.  Therefore any and all details may change significantly before the release of 2.8, so please be aware that nothing is yet finalized and as always, read the [release notes][1] once 2.8.0 ships.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update (Nov 17th, 2014):&lt;/strong&gt; Good news! I have re-tested with a patched version of 2.8.0-rc0 and the results are very encouraging compared to figure 2 below.  For full details (including an updated graph), see &lt;a href="https://comerford.net/2014/11/17/mongodb-2-8-improving-wiredtiger-performance/" target="_blank"&gt;MongoDB 2.8: Improving WiredTiger Performance&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Anyone that follows the keynotes from recent MongoDB events will know that we have demonstrated the concurrency performance improvements coming in version 2.8 several times now.  This is certainly the headline performance improvement for MongoDB 2.8, with concurrency constraints in prior versions leading to complex database/collection layouts, complex deployments and more to work around the per-database locking limitations.&lt;/p&gt;
&lt;p&gt;However, the introduction of the new &lt;a href="http://source.wiredtiger.com/2.4.1/index.html" target="_blank"&gt;WiredTiger&lt;/a&gt; storage engine that was announced at &lt;a href="http://www.mongodb.com/events/mongodb-london-2014" target="_blank"&gt;MongoDB London&lt;/a&gt; also adds another capability with a performance component that has long been requested: [compression][2]&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.eliothorowitz.com/" target="_blank"&gt;Eliot&lt;/a&gt; also gave a talk about the new storage engines at &lt;a href="http://www.eliothorowitz.com/blog/2014/11/03/mongodb-london-2014/" target="_blank"&gt;MongoDB London last week&lt;/a&gt; after announcing the availability of WiredTiger in the keynote.  Prior to that we were talking about what would be a good way to structure that talk and I suggested showing the effects and benefits of compression. Unfortunately there wasn’t enough time to put something meaningful together on the day, but the idea stuck with me and I have put that information together for this blog post instead.&lt;/p&gt;
&lt;p&gt;It’s not a short post, and it has graphs, so I’ve put the rest after the jump.&lt;/p&gt;</description></item><item><title>Finding the ReadAhead Sweetspot on an EBS Volume</title><link>https://comerford.net/2014/06/20/finding-the-readahead-sweetspot-on-an-ebs-volume/</link><pubDate>Fri, 20 Jun 2014 00:00:00 +0100</pubDate><guid>https://comerford.net/2014/06/20/finding-the-readahead-sweetspot-on-an-ebs-volume/</guid><description>&lt;p&gt;Setting readahead (RA from now on) appropriately is a contentious subject.  There are a lot of variables involved, but in my particular case I am setting out to minimize those variables, get a baseline, and have a reasonable idea of what to expect out of this configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Environment: Amazon EC2&lt;/li&gt;
&lt;li&gt;Instance Size: m3.xlarge (4 vCPU, 15GiB RAM)&lt;/li&gt;
&lt;li&gt;Disk Config: Single EBS Volume, 1000 PIOPS&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The testing I am going to be doing is pretty detailed, and intended for use in a future whitepaper, so I wanted to get some prep done and figure out exactly what I was dealing with here before I moved forward.  The initial testing (which is somewhat unusual for MongoDB) involves a lot of sequential IO.  Normally, I am tweaking an instance for random IO and optimizing for memory utilization efficiency – a very different beast which generally means low RA settings.  For this testing, I figured I would start with my usual config (and the one I was using on a beefy local server) and do some tweaking to see what the impact was.&lt;/p&gt;</description></item><item><title>My Conclusion from the Heartbleed Timeline</title><link>https://comerford.net/2014/04/15/my-conclusion-heartbleed-timeline/</link><pubDate>Tue, 15 Apr 2014 00:00:00 +0100</pubDate><guid>https://comerford.net/2014/04/15/my-conclusion-heartbleed-timeline/</guid><description>&lt;p&gt;&lt;a href="https://twitter.com/headhntr/status/455836463012139008" target="_blank"&gt;This tweet&lt;/a&gt; encourages people to read the timeline related to the Heartbleed discovery and dissemination and draw your own interesting conclusions – challenge accepted!&lt;/p&gt;
&lt;p&gt;There is plenty of fodder in there for the conspiracy theorists, but taking a step back for a second I would draw a conclusion not based on who knew what, but rather how to be one of those entities that knew early.  Why take that approach?&lt;/p&gt;</description></item><item><title>MongoDB 2.6 Shell Performance</title><link>https://comerford.net/2014/03/28/mongodb-2-6-shell-performance/</link><pubDate>Fri, 28 Mar 2014 00:00:00 +0000</pubDate><guid>https://comerford.net/2014/03/28/mongodb-2-6-shell-performance/</guid><description>&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; I have also written this up &lt;a href="http://stackoverflow.com/q/22719211/1148648" target="_blank"&gt;in Q&amp;amp;A format&lt;/a&gt; over on StackOverflow for visibility.&lt;/p&gt;
&lt;p&gt;When I am testing MongoDB, I often need to insert a bunch of data quickly into a collection so I can manipulate it, check performance, try out different indexes etc.  There’s nothing particularly complex about this data usually, so a simple &lt;code&gt;for&lt;/code&gt; loop generally suffices.  Here is a basic example that inserts 100,000 docs:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;for(var i = 0; i &amp;lt; 100000; i++){db.timecheck.insert({&amp;quot;_id&amp;quot; : i, &amp;quot;date&amp;quot; : new Date(), &amp;quot;otherID&amp;quot; : new ObjectId()})};&lt;/code&gt;&lt;/p&gt;</description></item><item><title>Testing MongoDB Over the WAN: Part 1</title><link>https://comerford.net/2014/03/11/testing-mongodb-over-the-wan-part-1/</link><pubDate>Tue, 11 Mar 2014 00:00:00 +0000</pubDate><guid>https://comerford.net/2014/03/11/testing-mongodb-over-the-wan-part-1/</guid><description>&lt;p&gt;This will be my first multi-part blog post, and I am actually not sure just how many parts it will have by the time I am finished.  My original intent was to test some failure scenarios whereby I would emulate a WAN link disappearing.  That quickly expanded into a more ambitious test, I still wanted to test failure scenarios but I also wanted to test with some real world (ish) values for latency, packet loss, jitter etc.&lt;/p&gt;
&lt;p&gt;In particular, I wanted to see how a sharded MongoDB cluster would behave with this type of variable performance and what I could do to make things better (I have some interesting ideas there), as well as test some improvements in the 2.6 version.  I’ve created configurations like this in labs with hardware (expensive), XenServer (paid) but I wanted something others could reproduce, reuse and preferably easily and at no cost.  Hence I decided to see if I could make this work with VirtualBox (I also plan to come up with something similar for Docker/Containers having read this &lt;a href="http://containerops.org/2013/11/19/lxc-networking/" target="_blank"&gt;excellent summary&lt;/a&gt;, but that is for later).&lt;/p&gt;
&lt;p&gt;My immediate thought was to use &lt;a title="Traffic Control HowTo" href="http://www.tldp.org/HOWTO/Traffic-Control-HOWTO/intro.html" target="_blank"&gt;Traffic Control&lt;/a&gt; but I had a vague recollection of having used a nice utility in the past that gave me a nice (basic) web interface for configuring various options, and was fairly easy to set up.  A bit of quick Googling got me to &lt;a title="WANem homepage" href="http://wanem.sourceforge.net/" target="_blank"&gt;WANem&lt;/a&gt; and this was indeed what I had used in the past.  I recalled the major drawback at the time was that after booting it, we needed to reconfigure each time because it was a live CD.  Hence the first task was to fix that and get it to the point that it was a permanent VM (note: there is a pre-built VMWare appliance available for those on that platform).&lt;/p&gt;
&lt;p&gt;That was reasonably straight forward, and I wrote up the process over at &lt;a title="SuperUser - adamc" href="http://superuser.com/users/113572/adam-c" target="_blank"&gt;SuperUser&lt;/a&gt; as a Q&amp;amp;A:&lt;/p&gt;
&lt;p&gt;&lt;a title="How to make WANem a Permanent VirtualBox VM" href="http://superuser.com/q/724551/113572" target="_blank"&gt;&lt;a href="http://superuser.com/q/724551/113572"&gt;http://superuser.com/q/724551/113572&lt;/a&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Once that was done, it was time to configure the interfaces, make routing work and test that the latency and packet loss settings actually worked (continues after the jump).&lt;/p&gt;</description></item><item><title>Bad Recruiting: Shutting Down an Interview Over Compensation</title><link>https://comerford.net/2014/02/10/bad-recruiting-shutting-down-an-interview-over-compensation/</link><pubDate>Mon, 10 Feb 2014 00:00:00 +0000</pubDate><guid>https://comerford.net/2014/02/10/bad-recruiting-shutting-down-an-interview-over-compensation/</guid><description>&lt;p&gt;I’ve meant to write this post up for a while.  I have spent a lot of my time in the last 2 years recruiting, interviewing, making offers etc. as I built a team up from nothing to 9 people.  I also interviewed for other positions in the company, helping others build out their teams.  It was very tough, at times it seemed there were no decent candidates out there, but with persistence and perseverance we would eventually get a good candidate over the line and my faith would be renewed.&lt;/p&gt;</description></item><item><title>More MongoDB Content – On StackExchange</title><link>https://comerford.net/2013/10/30/more-mongodb-content-on-stackexchange/</link><pubDate>Wed, 30 Oct 2013 00:00:00 +0000</pubDate><guid>https://comerford.net/2013/10/30/more-mongodb-content-on-stackexchange/</guid><description>&lt;p&gt;As mentioned previously, I like getting my little &lt;a title="Gamification – A New Twist on the Carrot and Stick" href="https://comerford.net/2012/03/01/gamification-a-new-twist-on-the-carrot-and-stick/" target="_blank"&gt;gamification rewards&lt;/a&gt; and I have been meaning to add new content here for quite some time.  In order to kill two birds with one stone, I took a couple of my ideas and turned them into the Q&amp;amp;A format that is encouraged on StackOverflow and the DBA StackExchange site.&lt;/p&gt;
&lt;p&gt;Hence we now have these two new questions (and answers):&lt;/p&gt;</description></item><item><title>MongoDB Melbourne and Sydney</title><link>https://comerford.net/2012/12/11/mongodb-melbourne-and-sydney/</link><pubDate>Tue, 11 Dec 2012 00:00:00 +0000</pubDate><guid>https://comerford.net/2012/12/11/mongodb-melbourne-and-sydney/</guid><description>MongoDB Melbourne and Sydney</description></item><item><title>In line for the #dailyshow wit…</title><link>https://comerford.net/2012/10/04/in-line-for-the-dailyshow-wit/</link><pubDate>Thu, 04 Oct 2012 00:00:00 +0100</pubDate><guid>https://comerford.net/2012/10/04/in-line-for-the-dailyshow-wit/</guid><description>&lt;p&gt;In line for the #[dailyshow][1]{.aktt_hashtag} with @[jekell][2]{.aktt_username} 🙂&lt;a href="http://t.co/js9jQgXi" rel="nofollow"&gt;&lt;a href="http://t.co/js9jQgXi"&gt;http://t.co/js9jQgXi&lt;/a&gt;&lt;/a&gt;
[1]: &lt;a href="http://search.twitter.com/search?q=%23dailyshow"&gt;http://search.twitter.com/search?q=%23dailyshow&lt;/a&gt;
[2]: &lt;a href="http://twitter.com/jekell"&gt;http://twitter.com/jekell&lt;/a&gt;&lt;/p&gt;</description></item><item><title>The crazy looking homeless lad…</title><link>https://comerford.net/2012/10/04/the-crazy-looking-homeless-lad/</link><pubDate>Thu, 04 Oct 2012 00:00:00 +0100</pubDate><guid>https://comerford.net/2012/10/04/the-crazy-looking-homeless-lad/</guid><description>&lt;p&gt;The crazy looking homeless lady has a nice speaking voice and a mobile phone #[newyork][1]{.aktt_hashtag}
[1]: &lt;a href="http://search.twitter.com/search?q=%23newyork"&gt;http://search.twitter.com/search?q=%23newyork&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Apparently that issue I closed…</title><link>https://comerford.net/2012/09/24/apparently-that-issue-i-closed/</link><pubDate>Mon, 24 Sep 2012 00:00:00 +0100</pubDate><guid>https://comerford.net/2012/09/24/apparently-that-issue-i-closed/</guid><description>&lt;p&gt;Apparently that issue I closed yesterday was number 1000 since I started @[10gen][1]{.aktt_username} in January, yay for round numbers! 🙂
[1]: &lt;a href="http://twitter.com/10gen"&gt;http://twitter.com/10gen&lt;/a&gt;&lt;/p&gt;</description></item><item><title>DUB to LCY again, this time to…</title><link>https://comerford.net/2012/09/11/dub-to-lcy-again-this-time-to/</link><pubDate>Tue, 11 Sep 2012 00:00:00 +0100</pubDate><guid>https://comerford.net/2012/09/11/dub-to-lcy-again-this-time-to/</guid><description>&lt;p&gt;DUB to LCY again, this time to see the brand new @[10gen][1]{.aktt_username} London office 🙂
[1]: &lt;a href="http://twitter.com/10gen"&gt;http://twitter.com/10gen&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Holy crap this is some match #…</title><link>https://comerford.net/2012/09/11/holy-crap-this-is-some-match/</link><pubDate>Tue, 11 Sep 2012 00:00:00 +0100</pubDate><guid>https://comerford.net/2012/09/11/holy-crap-this-is-some-match/</guid><description>&lt;p&gt;Holy crap this is some match #[usopen][1]{.aktt_hashtag}
[1]: &lt;a href="http://search.twitter.com/search?q=%23usopen"&gt;http://search.twitter.com/search?q=%23usopen&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>