3 ms·
It would be, were JetBrains IDEs currently compatible with the latest JDK, but they are not, so it's not quite as simple as that, unfortunately. IDEA and CLion
by gjvc 5y ago
It would be, were JetBrains IDEs currently compatible with the latest JDK, but they are not, so it's not quite as simple as that, unfortunately.
IDEA and CLion won't start with JDK 16 or later, so I'm using JDK 15 for those. All the other JetBrains IDEs work with JDK 16. In all cases, features using the JCEF [1] runtime library, which is bundled with the JBR [2], will not be available.
I'm using these options on Debian/unstable on all JetBrains IDEs, with both JDK 15 and JDK 16.
-XX:+IgnoreUnrecognizedVMOptions
-XX:+UnlockExperimentalVMOptions
-XX:+UseZGC
-XX:-UseG1GC
-XX:C1CompileThreshold=100
-XX:C2CompileThreshold=5000
-Xms4G
-Xmx4G
-XX:ReservedCodeCacheSize=512m
-XX:SoftRefLRUPolicyMSPerMB=50
-XX:CICompilerCount=2
--illegal-access=permit
Adding -XX:ReservedCodeCacheSize= and -XX:SoftRefLRUPolicyMSPerMB= made all the difference in keeping heap usage down. I have not yet experimented with different values for those parameters.
The option --illegal-access=permit is required on JDK 16, but this option was removed in JDK 17, and because of this (but probably not only this) I haven't yet been able to make any JetBrains IDE work with JDK 17.
In adjusting all of these settings, YMMV depending on your system. Good luck!
[1] https://github.com/JetBrains/jcef https://github.com/JetBrains/jcef
[2] which is currently based on JDK 11
- kaba0 5y agoWhile there are continuous performance improvements, between 15-17 it is probably not visibly so, but thanks for the config!