TL;DR Turn `DebugNonSafepoint` on by default everywhere. Turn if off ONLY if you see a regression (very uncommon).

yep I am discussing impact on activating DebugNonSafepoint in this blog post: jpbempel.github.io/2022/06/2…

"Why #JVM modern profilers are still safepoint biased?" Very interesting write-up by @jpbempel: while AsyncGetCallTrace avoids safepoint biasing, attribution of samples can still be biased due to lacking debug info; -XX: DebugNonSafepoint can help. jpbempel.github.io/2022/06/2…

New blog post: Why JVM modern profilers are still safepoint biased? #AsyncProfiler #JFR #HonestProfiler #AsyncGetCallTrace #DebugNonSafepoint jpbempel.github.io/2022/06/2…

I wish a JFR recording would ALWAYS turn on the -XX: DebugNonSafepoint flag... one more slippery detail to miss.

@ktosopl @kcpeppe @mauricenaftalin @pingtimeout great find. Be sure to set DebugNonSafepoint to JVM to get a more accurate profile.