I've used the ruby-prof and kcachegrind tools a few times to profile some of the rails projects I've worked on. They're powerful tools that can let you dig down into the bowels of your code and find the real trouble-makers, but they require a bit of familiarity as they really are a bit of information-overload. So I thought I could give a talk on how to set them up - where/how to use them and what they can do for you.

ABOUT TARYN EAST

More about Taryn East

ABOUT THE LONDON RUBY USER GROUP

LRUG is the London Ruby User Group; a community of ruby developers based in and around London. We meet up at least once a month; on the 2nd Wednesday of the month we have meetings with talks, demos and such-like and then we have pub-based meetups organised on an ad-hoc basis (roughly half-way between meetings). More about the London Ruby User Group