rmannibucau commented on pull request #26: URL: https://github.com/apache/commons-fileupload/pull/26#issuecomment-623415613
@GedMarc this sounds all wrong to be honest so you probably silent part of the process (which can be something you can't say publicly) cause jlink just does a custom JVM and put your jar in a .so, nothing more. Classloading gain is not that huge and breaks several libraries. In terms of perf cds i svery close to jlink images (you can measure it). Then runtime is almost 1-1 so any change can be a side effect of breaking the classpath URL for a particular library (so a wrongly configure application in jvm mode). In the 3 applications I migrated the gain was literally 0 once the JVM mode was aligned on the jlink mode. Also note that CDI/EE works well for microservices (less than 1s to start and be ready to serve, docker layer < 2M) and can even be made faster than jlink images with graalvm. Also on the modular point: you are NOT modular when doing a jlink image so fatjar is really the best option you can do today to avoid to fork all the ecosystem. It enables you to define all the JVm requirements and only keep the dependencies you want so you reach exactly you goal pretty quickly. Now I guess this is off topic for this thread and that jakarta distro must be enabled for commons but this has no link with jlink work and does not remove the fact javax stays mainstream for some years. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
