Posts

Showing posts with the label JavaOne12

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
Read more

JavaOne: The Summary

Image
So, JavaOne. Taylor Street Cafe I'm going to be controversial.  I think this was my favourite conference of this year.  I know that's not trendy, and that Oracle-bashing is still a popular pastime.  And I know I've also made a big deal about how much fun it is to meet people who program in different languages.  But there is something very special about being surrounded by thousands of people from all around the world who use the same technology as you, some facing the same problems, some solving very different issues. Maybe it's because since I first spoke at JavaOne last year I've met a lot of people in this ecosystem - Oracle Java people, other conference organisers, Java User Group leaders, speakers and attendees from all sorts of places - and seeing many of them in one place is fun and makes you feel like you're "home".  I'd be sat in the Taylor St Cafe area and people would sit down and hang out with me.  I'd be hiding somewher...
6 comments
Read more

JavaOne: The Problem With Women - A Technical Approach

Image
Yesterday dawned, with a sense of foreboding (actually it dawned with me coughing my lungs out, but we've heard enough about the sub-optimal state of my respiratory system this week).   On this day, I was giving the talk I was dreading when I got asked to do it.  It's the talk I actually put more work into than any of the other sessions I was presenting at this JavaOne.  It was the Women In IT talk. It's timely, given that conference season has one again led to cries of sexism and discrimination .  So although I really hate banging on about the subject (you'd never believe it from my blog) it's still necessary to cover. I feel, and have felt for a long time, that the way we're approaching the "problem" of the lack of women techies is just wrong.   Obviously painting stuff pink is just not going to cut it (I hope that's obvious).  I think the fundamental problem is that we keep thinking about women.  While that should be great for someone l...
22 comments
Read more

JavaOne: User Group Sunday

Image
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 ...
Post a Comment
Read more

Upcoming Events

So yeah... in keeping with this year's theme of basically only blogging about the exciting conferences I've been to, I'm going to blog about the exciting conferences I am attending in the future.  I haven't been great at doing that, the disconnect between the time I submit a presentation and the actual announcement means that I often forget I haven't told anyone about what I'm up to. Firstly, I'm back in the States this month to present my very first workshop - An Introduction to the Disruptor  at Strangeloop.  I've been given a mere 6 months to prepare it (note: sarcasm) and it's still a work in progress.  So, if you're coming, feel free to suggest things you want to see covered.  If you are coming, I'd love to hear from you. Secondly, I'm back in the States again a minute and a half later for several presentations at JavaOne.  I really enjoyed JavaOne last year, it was my first international conference, my first speaking gig, and a ...
Post a Comment
Read more

Popular posts from this blog

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: 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: Demystifying Memory Barriers

Image
My recent slow-down in posting is because I've been trying to write a post explaining memory barriers and their applicability in the Disruptor . The problem is, no matter how much I read and no matter how many times I ask the ever-patient Martin and Mike questions trying to clarify some point, I just don't intuitively grasp the subject. I guess I don't have the deep background knowledge required to fully understand. So, rather than make an idiot of myself trying to explain something I don't really get, I'm going to try and cover, at an abstract / massive-simplification level, what I do understand in the area.  Martin has written a post  going into memory barriers  in some detail, so hopefully I can get away with skimming the subject. Disclaimer: any errors in the explanation are completely my own, and no reflection on the implementation of the Disruptor or on the LMAX guys who actually do know about this stuff. What's the point? My main aim in this s...
Read more