-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is Java 17 recommended over 8 when 8 consistenly performs better? #39
Comments
use shenandoah gc on java 17 if java 8 managed to beat java 17 with it then check you arent using a debug build of java 17 and if you arent then i am amazed if java 8 has beaten java 17 in performance also newer versions of minecraft perform worse so if you are comparing minecraft 1.20 to 1.8 then 1.8 will perform better |
Using modded 1.16. I tried various versions from the piss poor performing Semeru to GraalVM EE. I did ignore Shenandoah because it's in only one Java that might perform bad, but I guess it's worth a try. Edit: I mean it's not in Oracle Java, which GraalVM EE is. I assume CE is the same, but I'll try it. |
I'm not making a RedHat account. BugMeNot blocks it because fuck you, so guess I'm just skipping it. |
shenandoah is included in most hotspot java builds (e.g not semeru or graal) java 11 onwards edit: do not use oracle's jdk builds they do not include shenandoah |
I've been benchmarking various flags, Java versions, etc, and in all of my testing nothing beats Java 8 with even stock options. I can only match Java 8 using stock flags with Java 17 using optimized flags.
The text was updated successfully, but these errors were encountered: