The case against passion

General

Something’s been bugging me lately. I’ve seen it said in otherwise intelligent blogs. I’ve seen it crop up more and more in resumes and job ads, to the point where it becomes something you have to say if you even want to be looked at, a piece of mindless dross taking up space on the paper or screen. I’ve seen it from managers who thought that it was an excuse to offer subaverage pay and conditions and demand unreasonable things from employees. I’ve seen it from people who should know better talking about how to educate and train engineers and programmers. I’ve been meaning to post about it for a while, but this post in It’s Common Sense, Stupid was the bit that finally got me to blog about it.… Read the rest

Read More
Mark Dennehy in 29 Comments

Cache conscious hash tables

GeneralJava

So one of the things I was working on as part of DeviceAtlas (but which ultimately didn’t get used) was a cache-conscious hash table in Java. It’s not unique in design – in fact it comes right out of a research paper written for the SPIRE 2005 conference by Nikolas Askitis and Justin Zobel – but the implementation was interesting to me as I’d not done optimisation work in Java in a while, and some things had changed quite a bit since I last wrote Java code. And it was a bit of an ego boost that I got it to outperform java.util.HashMap:

SUN HashMap fill: 57797 us
SUN HashMap query: 165701 us, 0 errors
CCHashTable fill (fair): 23205 us
CCHashTable query (fair): 35513 us, 0 errors
CCHashTable fill: 41723 us
CCHashTable query: 43055 us, 0 errors

Of course, there are the minor criticisms that it’s nowhere near as general-purpose as the HashMap class and that HashMap is arguably exhibiting an intelligent design choice rather than cheating per se, but I like my ego so I’m going to ignore those arguments!… Read the rest

Read More
Mark Dennehy in 11 Comments

s/365/364/

General

Hosting365 takes another nose-dive. Hosting364 is becoming more and more of an industry joke at this point. The last few crashes had unsatisfactory after-incident reports, and what little they showed demonstrated a lack of proper procedures (like testing machines to ensure that they recovered in the event of a power failure, or having redundant power feeds to racks, or having a backup nameserver that wasn’t sitting in the same room on the same power and net feeds of the primary nameserver).

This latest crash, caused by a failure in the air conditioning, saw the great PR move of informing everyone that only non-critical systems were down… including, apparently, the nameservers (both of which seem to still be in the same room on the same power and net feed), and most of the customers.… Read the rest

Read More
Mark Dennehy in 12 Comments