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

JavaOne: User Group Sunday



Well this is exciting!  JavaOne 2011 is the first conference I spoke at, so this the first time I've covered the same conference two years running.  I think.

It's very nice to be back at JavaOne.  Last year it was my first opportunity to meet so many people - the guys at Oracle who work really hard to make sure Java has its own identity; the JUG Leaders and Duchess folk; the JCP EC committee members; and loads of people who live and work in the area who I wouldn't normally get a chance to speak to in person.

This year I'm here with several other London Java Community people, and it's great to be a member of the Alumni, to have the privilege of showing other guys around and introducing people to each other.  It's nice to run into people I met here for the first time last year, some of whom I've had a chance to see at other events this year.

Today, Sunday, is an interesting day.  The focus is on community, so I get to hear what other JUGs are doing, some of their pain points, and learn some of the things they're doing that maybe we should think about.

The day started well, with Jim and Richard de-mystifying the business and technology terminology we're bound to come across at this conference.  8:15am is a really harsh time to have to do your first presentation, but it had a good turnout and was a great way to kick off the conference.

 I followed this with a talk about why you would open source your secrets, a short presentation detailing the benefits to your business of opening up parts of your codebase.  It went better than expected, given my voice has all but disappeared due to a stupid cold and plane travel and jet lag (and noisy bars).  I had contingency plans on how to present via typing or drawing on my iPad, but in the end I managed even despite the microphone not being turned on.  Doh.
There were a series of presentations on how to make your JUG successful and how to run Adopt a JSR/OpenJDK programmes in your user group, before Ben and I had to dash off to the public EC meeting.  This was not as well-attended as last year, but it meant that I had a chance to talk to all the EC members, and to drink more free champagne than one really ought to in the afternoon.


Next on the packed schedule was a trip to yet another location (seriously, that's 4 different locations just on Sunday) for the keynotes.  Note: next time I say "it's not far, let's walk" in San Francisco, hit me with sticks.  That's the second time in as many days I've been hit with a vertical distance that was further than the horizontal.  At least this time I wasn't wheeling my luggage up the hill like I was on Friday.

The keynotes were definitely better than last year.  I really enjoyed how the technical keynote put the shiny new stuff into an everyday context - seeing JavaFX running on all the platforms, including embedded, and seeing lambdas used in anger, was really engaging.  In my mind, it's much more likely to get "real" developers using these things.  I particularly enjoyed the interplay between Mark Reinhold and Brian Goetz, it's great to see people like that so passionate about what they're doing, it really humanizes them and their projects.

The last trip of the day was back down the hill to one of the many parties scheduled this week.  Of course, it's not in every party that you get given an award, so this was particularly sweet - the London Java Community has been honoured with a Duke's Choice Award.  This is the first year a community has won a "Dukey", and it's amazing to be part of a group of people who are actively contributing to the language I work with daily, and to be recognised for this.  So yes, I was on stage getting an award again.  It's addictive.

So, a really great kick off to this year's JavaOne, and I'm back at the apartment well before my coach (well, Uber) turns into a pumpkin and resting my voice in time for my Disruptor presentation tomorrow.


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 hea...
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...
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 n...
Read more