350 likes | 655 Views
Using Java Flight Recorder. Marcus Hirt Consulting Member of Technical Staff Michael Avrahamov Sr. Dir. Software Development. Agenda. Flight Recorder Overview Creating Recordings Analyzing Recordings Customizations Future.
E N D
Using Java Flight Recorder Marcus HirtConsulting Member of Technical Staff Michael Avrahamov Sr. Dir. Software Development
Agenda • Flight Recorder Overview • Creating Recordings • Analyzing Recordings • Customizations • Future
The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
Flight Recorder • High Performance Event Recorder • Built into the JVM • Binary recordings • Chunks • Self contained • Self describing • 101
Flight Recorder Advantages • Very detailed information • Extremely low overhead (<= 1%) • Can keep it always on, dump when necessary • Tooling for analysing recordings built into the Oracle JDK (Java Mission Control) • Java APIs available for recording custom information into the Flight Recorder in the Oracle JDK • Third party integration giving wholistic view of the detailed information recorded by the Flight Recorder (WLS, JavaFX)
Java Flight Recorder • Java Mission Control released with the 7u40 JDK • Java Mission Control 5.4.0 released with 8u20 • Java Mission Control 5.5.0 to be released with 8u40 • Most development effort is spent on Java Mission Control 6.0.0 - more on this later • Resulted from the JRockit and HotSpot JVM Convergence
Different Kinds of Recordings • Continuous Recordings • Have no end time • Must be explicitly dumped • Time Fixed Recordings (sometimes known as profiling recordings) • Have a fixed time • Will be automatically downloaded by Mission Control when done (if initiated by Mission Control)
How to Think About Recordings • A “recording” can both mean an ongoing recording on the server side, as well as a recording file. The context usually separates the two. • It might help to think of the server side recording as: • A named collection of event type settings… • …that are active for a certain period of time. • Recordings are collections of event type settings
How to Think About Recordings • A continuous recording R0 is started at T0 with settings S0. After a while, a time fixed recording R1 is started at T1 with settings S1, where S1 ⊃ S0. The time fixed recording R1 ends at T2. This is what will be recorded: If dumping R0 for a time range intersecting [T1,T2], you will get information that you did not ask for in the settings (S0). All this in the name of performance. Once T2 arrives, the settings for R1 will be popped, and we’re back to just recording S0. • Example
Different Kinds of Events • Instant Event • Data associated with the time the data was captured • Requestable Event • Polled from separate thread • Has a user configurable period • Duration Event • Has a start time and a stop time • Timed Event • Like Duration Event, but with user configurable threshold
Flight Recorder Inner Workings • Extremely low overhead • Using data already gathered • High performance recording engine • Testing! • Third party events • WLS • DMS • JavaFX • You can add your own! (Not supported yet.) • Performance, performance, performance
Preparations • Start the JVM from which to get recordings with: -XX:+UnlockCommercialFeatures -XX:+FlightRecorder • If remote monitoring is required: • Start with the appropriate com.sun.management flags • In 7u40 JDP can be used for easy discovery of manageable JVMs on the network • Hotspot
Creating Recordings Using Mission Control • Find a JVM to do a recording on in the JVM Browser • Double click the Flight Recorder node under the JVM • Follow the wizard (will show demo soon) Note: Ongoing recordings are listed as nodes under the Flight Recorder node. To dump one, simply drag and drop the ongoing recording to the editor area, or double click it. This is mostly useful for continuous recordings. • Easy and intuitive
Creating Recordings Using Startup Flags • Documentation of startup flags available in the JDK docs • The following example starts up a 1 minute recording 20 seconds after starting the JVM:-XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:StartFlightRecording=delay=20s,duration=60s,name=MyRecording,filename=C:\TEMP\myrecording.jfr,settings=profile • The settings parameter takes either the path to, or the name of, a template • Default templates are located in the jre/lib/jfr folder. • Note: Using the settings parameter will require either a JRockit or a Hotspot 7u40 or later. • To get more information on what is going on, change the log level:-XX:FlightRecorderOptions=loglevel=info • Useful for enabling continuous recordings at startup
The Default Recording • Special short hand to start the JVM with a continuous recording • Started with -XX:FlightRecorderOptions=defaultrecording=true • The default recording will have the recording id 0 • Only the default recording can be used with the dumponexit and dumponexitpath parameters • The following example will start up the continuous recording. It will be dumped when the JVM exits to C:\demos\dumponexit.jfr.-XX:+UnlockCommercialFeatures -XX:+FlightRecorder -XX:FlightRecorderOptions=defaultrecording=true,dumponexit=true,dumponexitpath=C:\demos\dumponexit.jfr • Shorthand for starting a continuous recording. With benefits.
Creating Recordings Using JCMD Usage: jcmd <pid> <command> Example starting a recording:jcmd 7060 JFR.start name=MyRecording settings=profile delay=20s duration=2m filename=c:\TEMP\myrecording.jfr Example checking on recordings:jcmd 7060 JFR.check Example dumping a recording:jcmd 7060 JFR.dump name=MyRecording filename=C:\TEMP\dump.jfr • Useful for controlling JFR from the command line
Enterprise Production Environments Tight Security protocols with respect to access to JVMs Large sets of JVMs on different life cycles • Test • Pre production (stage) • Production Admins top priority: resume service delivery • Automate discovery • Automate and simplify collection Developers prefer to investigate in their habitat
Oracle EM – secure access Problem: Dev needs access to JVM/JFR in production IT Requirements: Authentication who is allowed? Authorization What can they do? Which target/objects can they manage/see? Audit What have they done? Benefit: Admin can allow developers controlled and audited access to JVMs in production
Oracle EM – Enterprise scale • Manage all JVMs across enterprise (monitor, track changes, diagnose)
Analyzing Recordings DEMO
Some Common Pitfalls • Not accounting for thresholds • Thresholds are very useful for keeping performance up but still detecting outliers • Can be confusing. Example:Thread T has been running for 2 minutes and sum of latencies is a minute. Was the thread T running unblocked for a minute? • Not accounting for CPU load • Don’t make decisions based on method profiling data if there is no load • If you have full load, then looking at latencies may be a waste of time
Programmatically Analyzing Flight Recordings • The parser included in Mission Control can be used to analyze recordings programmatically • If enough people want to, I can write a blog on how it can be used • The JMC team also have an experimental JDBC bridge • Using the JMC parser (Unsupported)
Minimizing Object Creation • Can reuse event objects • Use with care – only where you know it’s thread safe !
Built in GUI editor (unsupported) • The JMC has a built in designer • Can be used to both customize the existing GUI and produce entirely new GUIs for events • The created GUIs can be exported as plug-ins and shared
Quick roadmap • JMC 5.5.0 (8u40) • Dynamic enablement of Flight Recorder (no startup flags needed) • Hiding of Lambda Form methods • JMC 6.0.0 (JDK 9) • Automatic analysis of Flight Recordings • Greatly revised user interface (more modern, cleaner) • Continually • New event types (improved I/O events, GC events, loaded libraries) • Near, mid future
Other Resources • Plus shameless book plug • JMC Homepagehttp://oracle.com/missioncontrol • Hirt’s bloghttp://hirt.se/blog • Twitter@javamissionctrl, @hirt • Shameless Book plug • EM – go to OTN