Memory Consumption: WildFly Full ThinWAR vs. Quarkus SkimmedJAR

Comparing the memory consumption of WildFly 18.0.1.Final (Java EE Full & Web Distribution) and Quarkus by deploying identical microprofile application to both runtimes:

The ThinWAR project was created with Jakarta EE Essentials Archetype, the 6kB ThinWAR was built and deployed with: in 3.1s.

The Quarkus Runner 20.3kB "SkimmedJAR" was built in 4.3s from scratch. The file size of the native executable was 32 MB, the built took 53.7s.


The performance seamed to roughly triple as well with the native version. Although that could be maybe be explained by caching.

Posted by Joakim Zetterberg on January 14, 2020 at 01:35 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments