AOT Map changes during production run

[María Arias de Reyna Dominguez]

Hi!

I have a question.  I did a training run and generated what looks like a
valid cache.

Summary of the number of elements (for certain types of elements) the map
contains:
```
Classes in AOT Cache: 10.885
Methods in AOT Cache: 121.393
  -> ConstMethods: 121.293
  -> MethodCounters: 6.530
  -> MethodData: 4.127
ConstantPool: 10.197
  -> ConstantPoolCache: 10.197
```

And then I did a production run using the generated cache, which replaced
the `aot.map` with a new one that is much smaller:

```
Classes in AOT Cache: 3.431
Methods in AOT Cache: 38.359
  -> ConstMethods: 38.359
  -> MethodCounters: 0
  -> MethodData: 0
ConstantPool: 3.067
  -> ConstantPoolCache: 3.067
```

As you can see, there are a lot of missing elements!

If I check the md5sum of the actual cache file before and after the
production run, it stays the same. It is the AOT Cache Map which changes.
Is that... supposed to happen?

Maybe it is a bug related to https://bugs.openjdk.org/browse/JDK-8362566 ?

Both map files start with `AOT cache map for app.aot`, it is not the map
file for the `app.aot.config` that appears during the training run.

Both the training and the run were the same: just spin up an Infinispan
server and shut it down after a few seconds. But I guess that's irrelevant
because the aot cache file is exactly the same.

I could stop generating the aot map file on the production run because
there is no need for it, but I forgot to remove it... and then this
happened.

Kind regards,
María Arias de Reyna Domínguez
Senior Software Engineer
She / Her / Hers
ariasdereyna at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/leyden-dev/attachments/20251008/1d27d95a/attachment.htm>