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
I noticed that when there are a lot of classes (>200 in my case) the java_package procedural macro takes several tens of seconds to run. I suspect that this is because for each class duchess spawns a new javap process, which in turns runs a full JVM.
Check if the bottleneck is really javap.
If the bottleneck is javap, it should be possible to keep reusing the same JVM by using the Java interface of javap.
The text was updated successfully, but these errors were encountered:
The flamegraph of a cargo build confirms that 66% of the samples are in the JVM (start_thread). Within the JVM, 54% of the samples are in the Java compiler (CompileBroker::invoke_compiler_on_method).
I noticed that when there are a lot of classes (>200 in my case) the
java_package
procedural macro takes several tens of seconds to run. I suspect that this is because for each classduchess
spawns a newjavap
process, which in turns runs a full JVM.javap
.javap
, it should be possible to keep reusing the same JVM by using the Java interface ofjavap
.The text was updated successfully, but these errors were encountered: