Posts

Showing posts with the label events

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

First presentation at the Virtual JUG!

Image
Yesterday I had the privilege of presenting the very first session for vJUG, a new virtual Java User Group that allows us to span geographies when sharing talks and stories.  I'm really interested in the vJUG idea, especially now I'm not in London - if we can find good ways to share knowledge without having to travel, that will help us reach people who don't normally go to conferences or don't have a local user group to go to.  Not to mention cutting travel costs and saving the environment. See the event, and the record of the IRC chat, here:   The slides are also online, but obviously they're part of the video as well: Design is a process, not a Document from Trisha Gee
1 comment
Read more

Trisha's World Tour 2013

Quick update on my scheduled events this year.  Please feel free to suggest your MUG or JUG or other tech group as somewhere for me to visit on this Grand World Tour if I'm in your city. 17-21st June - In New York - woohoo!  Getting to know Justin Lee , the newest member of the Java team, doing some pair programming (hopefully) and meeting people at the MongoDB Masters' Summit on Thursday. 24th June - STAC Summit , London - I'm not presenting, but I'll be there "networking" (a.k.a. drinking) 27th June - Technology Transformation Network , London.  Tiny bit concerned about this event now (don't tell anyone) because I'm hoping to run break out sessions on how to approach design, and I'm not sure I can do this alone.... 1-5th July - In Dublin, hoping to talk to a MUG or JUG while I'm there.  Invite me! 22-25th July - JavaOne Shanghai (CON1148). I've never been east of Europe before, very exciting. August - Going to be in Seville (Spain), a...
2 comments
Read more

2013 is looking a lot busier than I planned...

So, despite promising myself that I would only do one event a month for the rest of this year, looks like I'm going to be a bit busier than that. In case you're wondering what I'm up to (or, even better, hoping to see me talk or meet me), here are my confirmed engagements: 15-17 May - GeeCon , Poland 18-20 June - GOTO Amsterdam - whole day tutorial on the new (unfinished) MongoDB Java driver. 24th June - STAC Summit , London - something MongoDB-shaped (i.e. not Java-specific) 27th June - Technology Transformation Network , London 1-5th July - In Dublin, hoping to talk to a MUG or JUG while I'm there. 22-25th July - JavaOne Shanghai (CON1148). So excited to go to China! August - Looks like I'm going to be in Spain a couple of times (Madrid/Seville). 11-12th Sept - Love to go to JavaZone, Oslo.  We'll see. 22-26 Sept - JavaOne , San Francisco. 30th Sept - 2nd Oct - GOTO Aarhus - very pleased I can make it this year! 17-18th Oct - GOTO Berlin . ...
2 comments
Read more

Upcoming Events

Time for another ad-hoc update on what I'm up to: Thur Oct 25th: LJC JavaOne Circleback Event Thur Nov 1st: The Problem With Women - A Technical Approach Wed 14th November - Devoxx : Why Open Source Your Secrets , Agile++: When Agile Goes Well Sat 24th November: LJC Open Conference Thur 29th November: My first MongoDB Webinar .   I'm also going to be in New York for training from the 5th - 9th November, but I can't swear to my availability during that time - apparently training is going to take up the days, and the evenings I'm going to try and get a jump start on some actual code.
Post a Comment
Read more

Mike and I debut our new Disruptor presentation

Last Tuesday  Mike and I unveiled our brand shiny new presentation: Understanding the Disruptor, a Beginner's Guide to Hardcore Concurrency .  This was a preview of the talk we'll be doing at JAX London on the 2nd November. A video of the session is available, as are the slides .  I promise not to say "so" anywhere near as many times when I repeat my performance at JAX (is there anything more painful than watching yourself on video?). I thought the session went really really well.  We got some great questions at the end, we had an audience that was engaged, and I was dead pleased we didn't lose anyone with the assembly language.  We had some very valuable feedback afterwards too. As well as our presentation, there were three great lightning talks: Somay Nakhal on Java Thread States - Somay gave a nice overview of thread lifecycles with code and some great diagrams.  I liked how he made this more applicable to the real world than the sort of...
4 comments
Read more

My first public appearance

I'm finally moving up from working behind the scenes to actually doing a (short) presentation for the LJC. I'm going to be giving a lightning talk on Wednesday at the AWS Elastic Beanstalk event , on the JCP - what it is and what our election to the executive committee means.   Ben and Martin's post  gives a little more background on the subject. Another LMAX LJC member  Mike will also be giving a lightning talk, on Project Coin. Now all I have to do is write it...
1 comment
Read more

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: 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