copper vortex
from that issue
I think, generally, it's a bad idea to for Prism to offer "better defaults" especially considering there's no guarantee that the user's specific hardware and software configuration would benefit from the proposed defaults. I'd also like to softly demand we prove that the chosen defaults are generally beneficial on their own and in whole before putting them forth as necessarily better. To say nothing of differences between JVMs like OpenJDK and Oracle's JVM
i saw the comment after that one too but didn't really have anything to say there
young orbit
the jvm has much better defaults than it did in the 1.7.10 days
on modern systems the difference you can get is pretty small
and even on older ones almost everything is a tradeoff (otherwise they'd just be the default in the jvm)
the only thing that's mostly consistently a win is shenandoah instead of g1gc
and that's not supported by a number of jvm distributions
-XX:+AlwaysActAsServerClassMachine is probably a mostly universally good idea? by default the jvm changes a bunch of settings to optimize for startup time and ram usage instead of throughput on very low-end machines, which is probably not desirable for minecraft
("very low-end" = ≤2c4t CPU && ≤2GB RAM)
from experience: for modded those specs are just barely enough for 1.7.10 with heavy manual optimization
I'm honestly unconvinced that 2GB system RAM is enough for anything modern