You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Temurin was chosen as the Java runtime for the elk stack, as Temurin is the successor to AdoptOpenJDK, which tweaked the JVM in ways that were advantageous for our use case. However, with the transition to Eclipse Foundation stewardship, the goals of the project have changed, so Temurin does not actually carry forward these changes to the JVM, and is, in fact, a pretty vanilla distribution of OpenJDK.
Therefore, we may as well be using the distro-provided packages for the Java runtime. I've opened #36 to make this change, but given that performance has become a concern for the audit plugin, it still may be worth using a Java runtime more tailored to our needs. After doing a little bit of research, it appears that GraalVM CE may be the way to go.
The text was updated successfully, but these errors were encountered:
Temurin was chosen as the Java runtime for the elk stack, as Temurin is the successor to AdoptOpenJDK, which tweaked the JVM in ways that were advantageous for our use case. However, with the transition to Eclipse Foundation stewardship, the goals of the project have changed, so Temurin does not actually carry forward these changes to the JVM, and is, in fact, a pretty vanilla distribution of OpenJDK.
Therefore, we may as well be using the distro-provided packages for the Java runtime. I've opened #36 to make this change, but given that performance has become a concern for the audit plugin, it still may be worth using a Java runtime more tailored to our needs. After doing a little bit of research, it appears that GraalVM CE may be the way to go.
The text was updated successfully, but these errors were encountered: