RFR: 8364372: [Leyden] Set UseAOTCodeLoadThread ergonomically [v2]

Ashutosh Mehra asmehra at openjdk.org
Thu Jul 31 14:04:15 UTC 2025


On Thu, 31 Jul 2025 14:01:38 GMT, Ashutosh Mehra <asmehra at openjdk.org> wrote:

>> Without this fix:
>> 
>> [assembly phase]
>> $ java -Xlog:jit+thread=debug -XX:AOTMode=create -XX:AOTCache=jbench.aot -XX:AOTConfiguration=jbench.aotconf -cp JavacBench.jar JavacBench 100
>> ...
>> [0.317s][debug][jit,thread] Added initial compiler thread C1 AOT code caching CompilerThread
>> [0.317s][debug][jit,thread] Added initial compiler thread C2 AOT code caching CompilerThread
>> ..
>> 
>> With this fix, these threads are only in the production phase, not in the assembly phase.
>
> Ashutosh Mehra has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Review comments
>   
>   Signed-off-by: Ashutosh Mehra <asmehra at redhat.com>

I also wonder why we set `AOTReplayTraining` to true in assembly phase in `cdsConfig.cpp`?
https://github.com/openjdk/leyden/blob/392fbbb1859cd71521cb915b601a65cf59ba495b/src/hotspot/share/cds/cdsConfig.cpp#L790

Isn't replay training only required in a production run?

-------------

PR Comment: https://git.openjdk.org/leyden/pull/89#issuecomment-3140098164


More information about the leyden-dev mailing list