GOTO is a vendor independent international software development conference with more that 90 top speaker and 1300 attendees. The conference cover topics such as .Net, Java, Open Source, Agile, Architecture and Design, Web, Cloud, New Languages and Processes

Rickard Bäckman, Oracle

Rickard Bäckman

Biography: Rickard Bäckman

Rickard Bäckman has over 10 years of software development experience in many areas, for example the online trading industry and financial systems. He has worked at Oracle on Java Flight Recorder since 2010, and is currently a JIT compiler engineer in the HotSpot JVM team. He is located in Stockholm. Rickard has a computer science degree from KTH, the Royal Institute of Technology in Stockholm, Sweden.

Twitter: @r_ba

Presentation: Java Flight Recorder - Next generation diagnostics and profiling

Track: Java Tools / Time: Monday 14:30 - 15:20 / Location: Kammermusiksalen, Musikhuset

Have you ever deployed software to your production environment containing System.out.println() to track down a hard to find deadlock? Or to find out where all those allocations that caused your JVM to choke on GC happend? What were the I/O calls that took forever to complete?

Java Flight Recorder is a new feature in the JVM, designed to be always on in a production system, it provides user with a lot of information of how the JVM and the application is behaving at a very low overhead. Together with Java Mission Control it gives the user with new ways of finding those hard-to-track-down problems without deploying new code.
Maybe best of all, you can reconfigure it, start it and stop it fully in flight. There is no longer any need to recompile and restart your production system in order to profile it - and the profiling itself is low overhead enough not to affect your quality of service level.

We will talk about the different concepts in Java Flight Recorder, how to use and configure it as well as the implementation details, and how it differs from other solutions.

What's the architecture that enables Java Flight Recorder to be a low overhead JVM inspector / profiler?
How is data collected, what does it look like in memory? On disk? How did the problems, requirements and solutions play together to make Java Flight Recorder what it is.