This Blog Has Moved!

Right, so yes, five years ago I moved to github pages, and never bothered to redirect any of these pages there. Now I've moved on from there, and... Finally I am using my real domain, trishagee.com . My blog is now at trishagee.com/blog .  See you there!
Post a Comment

The Strange Loop

Last week (was it only last week?) I was at Strange Loop, presenting a workshop on the Disruptor.

I didn't really have any expectations from the conference, I've never been before and, if I'm honest, hadn't heard of it before.  So everything was a pleasant surprise.

It's a very geeky conference.  I mean that as a compliment, of course.  Lots of very smart people talking about stuff that's waaaay more advanced than you frequently get in the conferences employers would be happy to pay for.  The themes I mostly saw were functional programming and the (insert horribly abused term) Big Data space.

So nothing about Spring and Hibernate or any of their ilk, of course.  Almost nothing about Java actually, as if a language that is actually used by millions of developers is somehow too passé.  But this was extremely liberating - if there's nothing that's going to be applicable to my day job, I can go and see talks on things I'm actually interested in.  That's not to say the day job is not interesting, of course, but removing the constraint meant the only criteria for selecting talks was "Will I learn something I didn't know before?".

My favourite talk was Jeff Hawkins' keynote, Computing Like the Brain.  It was as if he was trying to download several decades of research on neuroscience into our brains in less than 30 minutes.  It was incredible!  Fascinating, and the stuff of science fiction.

The quality of speakers was really good, big names that many would recognise, all talking about their passions.  And it was another friendly conference, where lots of people appeared to be there on their own, and were happy to get chatting to randoms like me.

There were a lot of people too.  I had expected it to be quite a small, intimate conference.  But while it's not JavaOne, there were a lot more people than I expected.

I've never been to St Louis before either.  However, since I voluntarily spent all my time between the hotel and the venue, I think I can safely say I still haven't really been there.  But the venue and the hotel were really beautiful places, as well as being dead conveniently placed.

So I enjoyed Strange Loop.  It was a little strange, and I was out of my comfort zone, but I had an interesting time and met yet more great people.  I'd love to go again next year, if I get the chance (hint hint).

Comments

Post a Comment

Comments have been disabled since this blog is no longer active.

Popular posts from this blog

Dissecting the Disruptor: What's so special about a ring buffer?

Image
Recently we open sourced the LMAX Disruptor , the key to what makes our exchange so fast.  Why did we open source it?  Well, we've realised that conventional wisdom around high performance programming is... a bit wrong. We've come up with a better, faster way to share data between threads, and it would be selfish not to share it with the world.  Plus it makes us look dead clever. On the site you can download a technical article explaining what the Disruptor is and why it's so clever and fast.  I even get a writing credit on it, which is gratifying when all I really did is insert commas and re-phrase sentences I didn't understand. However I find the whole thing a bit much to digest all at once, so I'm going to explain it in smaller pieces, as suits my  NADD audience. First up - the ring buffer.  Initially I was under the impression the Disruptor was just the ring buffer.  But I've come to realise that while this data structure is at the heart of the patte
Read more

Dissecting the Disruptor: Writing to the ring buffer

Image
This is the missing piece in the end-to-end view of the Disruptor.  Brace yourselves, it's quite long.  But I decided to keep it in a single blog so you could have the context in one place. The important areas are: not wrapping the ring; informing the consumers; batching for producers; and how multiple producers work. ProducerBarriers The Disruptor code has interfaces and helper classes for the Consumer s, but there's no interface for your producer, the thing that writes to the ring buffer.  That's because nothing else needs to access your producer, only you need to know about it.  However, like the consuming side, a ProducerBarrier is created by the ring buffer and your producer will use this to write to it. Writing to the ring buffer involves a two-phase commit.  First, your producer has to claim the next slot on the buffer.  Then, when the producer has finished writing to the slot, it will call commit on the ProducerBarrier . So let's look at the first bi
Read more

Dissecting the Disruptor: How do I read from the ring buffer?

Image
The next in the series of understanding the Disruptor pattern developed at LMAX . After the last post we all understand ring buffers and how awesome they are.  Unfortunately for you, I have not said anything about how to actually populate them or read from them when you're using the Disruptor. ConsumerBarriers and Consumers I'm going to approach this slightly backwards, because it's probably easier to understand in the long run.  Assuming that some magic has populated it: how do you read something from the ring buffer? (OK, I'm starting to regret using Paint/ Gimp .  Although it's an excellent excuse to purchase a graphics tablet if I do continue down this road.  Also UML gurus are probably cursing my name right now.) Your Consumer is the thread that wants to get something off the buffer.  It has access to a ConsumerBarrier , which is created by the RingBuffer and interacts with it on behalf of the Consumer .  While the ring buffer obviously needs a se
Read more