Replies: 2 comments 4 replies
-
|
Sound very interesting, The feature page states this is experimental do you know if this is safe for production, or will this be an optional flag? |
Beta Was this translation helpful? Give feedback.
-
|
CDS is enabled by default and a production feature in the latest JVMs. We would need to bump the JDK version in our side (e.g.: image) too and find the version we should be using because there were improvements over time around CDS. |
Beta Was this translation helpful? Give feedback.
-
|
I did some experiments recently and was not too impressed with the results. With ADS/CDS I could only shave off a few 100ms startup time. |
Beta Was this translation helpful? Give feedback.
-
|
For me, it saves about 1s. Also, not this is about memory footprint too, something I did not check yet. One key difference here is that I'm using JDK 13+. Can you try it using the same version? Could you also try running locally (not as a container)? |
Beta Was this translation helpful? Give feedback.
-
|
I only tested this with JDK 17. Between Java 11 and Java 17 I could observe a decent reduction in startup time (~1s - 1.5s) from switching to JDK 17 alone. Do you think it make sense to test the intermediate JDK versions as well? Most customers that I known only use a LTS version, e.g. JDK11 or JDK17 for running Keycloak in production. But I can for sure try this with older JDKs as well. |
Beta Was this translation helpful? Give feedback.
-
|
I think we should track the latest releases to make sure the improvements are there and justify the investment. In the worst case, we can create/update a guide with some instructions about how to optimize runtime using this approach? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
To help reduce startup time and memory footprint, I would like to propose introducing a CDS archive into the distribution based on the classes loaded when running a JVM for a "naked" distribution.
Although we are not really interested in sharing the archive across multiple JVM processes running on a host, it should help to load classes faster. I'm still evaluating how much we should save.
There are several ways we can generate the CDS archive from Maven by using Quarkus CDS support.
We can also start doing this only for container images and not necessarily include the archive in the distribution. That should improve the experience when running as a container given the resource constraints. In this case, we would be creating the CDS archive into the base image and setting the necessary JVM options to enable CDS.
Beta Was this translation helpful? Give feedback.
All reactions