You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in FSD mode the JIT fails to compile certain methods containing method handles. The resulting time spent in the interpreter for these methods can cause a significant performance difference compared to not running in FSD. This obviously impacts developer experience when needing to run significant code before reaching the code to be debugged.
(Mistaken statements about agents removed)
The text was updated successfully, but these errors were encountered:
wider consequences with the increasing prevalence of agents that late attach and therefore need to perform class redefinition.
I don't think I understand the connection here. For quite a few years now it has been possible by default for an agent to late attach and redefine classes. This doesn't require debug mode
I'd have to go back over my notes, but I'm reasonably confident that one of the recent cases related to running in FSD as a result of class redef.
Went back over my notes, I was wrong. The case was caused by the combination of FSD and the late attached agent, not FSD being caused by the agent doing redef.
When running in FSD mode the JIT fails to compile certain methods containing method handles. The resulting time spent in the interpreter for these methods can cause a significant performance difference compared to not running in FSD. This obviously impacts developer experience when needing to run significant code before reaching the code to be debugged.
(Mistaken statements about agents removed)
The text was updated successfully, but these errors were encountered: