JEP 515: Ahead-of-Time Method Profiling, how to generate the profiles on hot methods?

[Daniel Andres Pelaez Lopez]

Hi everyone,

>From JEP 515: Ahead-of-Time Method Profiling, I read the following:

"the AOT cache now also stores method profiles that the JVM would otherwise
need to collect in the early part of an application's run"

And

"The net effect of cached profiles is that the JIT runs earlier and with
more accuracy, using the profiles to optimize the hot methods so that the
application experiences a shorter warmup period"

My question is: what's need it to generate the profiles on the training
run? My understanding is that JIT requires to see a hot method being
executed hundreds of times to later optimize it, if we need to replicate
that behavior on a training run, it means we need to load tests the app
over what we think are the hot paths.

If JEP 515 only needs one training run of the hot path, instead of
hundreds, the training run complexity will decrease, as it requires not a
load test, but just a smoke test.

I would like to understand better how the training run should behave for
this JEP.

Regards

-- 
Daniel
e. estigma88 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/leyden-dev/attachments/20250513/30dacaa1/attachment.htm>