JFR-based remoting flight recorder #26282

This commit is contained in:
Johan Andrén 2019-12-16 11:45:13 +01:00 committed by GitHub
parent 02db62bd73
commit 8a019f86a1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
25 changed files with 920 additions and 256 deletions

View file

@ -864,3 +864,12 @@ spec:
There is currently no way to limit the size of a memory empty dir but there is a [pull request](https://github.com/kubernetes/kubernetes/pull/63641) for adding it.
Any space used in the mount will count towards your container's memory usage.
### Flight Recorder
When running on JDK 11 Artery specific flight recording is available through the [Java Flight Recorder (JFR)](https://openjdk.java.net/jeps/328).
The flight recorder is automatically enabled by detecting JDK 11 but can be disabled if needed by setting `akka.java-flight-recorder.enabled = false`.
Low overhead Artery specific events are emitted by default when JFR is enabled, higher overhead events needs a custom settings template and are not enabled automatically with the `profiling` JFR template.
To enable those create a copy of the `profiling` template and enable all `Akka` sub category events, for example through the JMC GUI.

View file

@ -206,7 +206,7 @@ In the thread state diagrams below the colours have the following meaning:
* Green - Runnable state
The thread information was recorded using the YourKit profiler, however any good JVM profiler
has this feature (including the free and bundled with the Oracle JDK VisualVM, as well as Oracle Flight Recorder).
has this feature (including the free and bundled with the Oracle JDK [VisualVM](https://visualvm.github.io/), as well as [Java Mission Control](https://openjdk.java.net/projects/jmc/)).
The orange portion of the thread shows that it is idle. Idle threads are fine -
they're ready to accept new work. However, large amount of turquoise (blocked, or sleeping as in our example) threads