On Sat, 26 Apr 2025 22:42:02 GMT, Vladimir Kozlov <k...@openjdk.org> wrote:
>> Improve warm-up time by making profile data from a previous run of an >> application instantly available, when the HotSpot Java Virtual Machine >> starts. Specifically, enhance the [AOT cache](https://openjdk.org/jeps/483) >> to store method execution profiles from training runs, reducing profiling >> delays in subsequent production runs. >> >> More details in the JEP: https://bugs.openjdk.org/browse/JDK-8325147 > > src/hotspot/share/oops/trainingData.cpp line 76: > >> 74: >> 75: static void verify_archived_entry(TrainingData* td, const >> TrainingData::Key* k) { >> 76: guarantee(TrainingData::Key::can_compute_cds_hash(k), ""); > > Should we gracefully disable using TD instead of crashing VM? But this is a verification code. That seems to be the usual strategy, is it not? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/24886#discussion_r2061847152
