Gather build-time data in JVM-mode like we do in native-mode about quarkus HOT 2 OPEN

Are the native mode numbers based on the final class list after dead code elimination?

Yes the numbers we collect from native builds are what ends up being included in the native executable.

In JVM mode we don't currently do any DCE (though I have some ideas about this)

Certainly there is no DCE, but you still have some dependencies that are only on the build classpath.

so I don't know that this will tell us a whole lot about image size.

Correct, this is not meant to be used for getting any insight about the image size. The motivation was to be used for keeping an eye on how many classes/packages we add on the runtime classpath and how much this is changing over time (e.g. because of library updates). This could be an indication of how bigger or smaller containerized quarkus applications become over time.

Such metrics are not necessarily tied to performance, but we have noticed that the native executable for a simple hello world has been gradually increasing over the years. I wonder if this is the case for jvm-mode containerized applications.

from quarkus.

Are the native mode numbers based on the final class list after dead code elimination? In JVM mode we don't currently do any DCE (though I have some ideas about this), so I don't know that this will tell us a whole lot about image size.

from quarkus.