On Tuesday 5th June we’re running a new event focused on Java Memory Leaks, and in particular, solving these in under 10 minutes (sounds good to us!). We’ll be using a consistent methodology to identify whether you have a heap memory leak, analysing the memory to identify the leak, and determining the cause.
We’re delighted that we’ll be joined at the event by Jack Shirazi from the Performance and Reliability team at Hotels.com. Alongside his role at Hotels.com, Jack is the founder of JavaPerformanceTuning.com and author of Java Performance Tuning (O’Reilly); he’s been an official Java Champion since 2005 and an LJC member since 2009. As well as authoring his popular book, and contributing to several other books, Jack has published over 60 articles on Java performance for various sites and magazines; over 200 newsletters for JavaPerformanceTuning.com over 15 years; and, with these newsletters published around 10,000 Java performance and memory related tips.
Ahead of the event we caught up with Jack; he told us why the session is important, what questions we can expect to learn the answers to and gave us his advice for new developers.
1. Who do you think should come along?
Any Java developer of any level. I provide sufficient detail for any level of developer and this talk shows how to solve a problem that is intermittent, so even if you’ve analysed heaps before it’s useful to get a different point of view and a refresher
2. What do you think are the three most interesting questions that this event will answer?
The event answers: what process you should follow for analysing any Java memory leak; which tools are most useful for analysing Java heap leaks; and how you can identify that you have a leak before (as well as after) a leak becomes an issue.
3. Why do you think this presentation is important for people?
Memory leaks are one of the most common causes of downtime/server crashes/service failure. But, at least for heap leaks, they’re a solved problem – you just need to know what to do about them. But leaks don’t happen often enough that every Java developer will have or remember the skillset to solve the problem quickly. What I’m providing is a step-by-step procedure that you can easily understand then forget about until you need it – then just quickly refresh yourself in minutes and apply to solve the issue very quickly.
4. Any advice for junior developers entering the industry?
Come to this session and add this to your toolset. Then remind yourself before you have an interview, experience of fixing a memory leak is a cool thing to know for interviews.
If you’d like to join us at the event it’s on 5th June, 18:30 – 20:30 at WeWork Old Street, N1 6DR. The event is kindly being sponsored by the folks at Gridgain, WeWork Old Street and RecWorks. You can find all the registration details here: https://www.eventbrite.com/e/become-a-guru-how-to-solve-java-memory-leaks-in-under-10-minutes-tickets-46143517503