In Notes 14 and Domino Designer 14, java has been updated to Java 17.
Yet upon inspection of jvm.properties, it still thinks it is in 2009.
Please update.
Xmx: too low, because the 64bit datastructures are bigger. Suggest at least doubling or quadrupling for Designer (so 1024m or 2048m). Doubling for Client, so 512m.
Xms: to high, an early gc forcing out boot only structures promotes health. Suggest 128m
Dosgiext => underlying log framework needs fix for change very very long time ago
Xscmx64m, very old size stemming from 2009. Current 64bit default is 300m, works much better. Suggest to NOT set it and let the JVM decide.
Xmaxaot12m, very old max. Suggest to NOT set it and let the JVM decide.
Xminf0.1, old. Suggest to NOT set it and let the JVM decide.
Xmn7m, very old. Hampers proper nursery. Suggest to NOT set it and let the JVM decide.
XShareclasses, odd beast. The J9 docs does not list most parameters used. I've tried using documented parameters with only partial success. Suggest removing singleJVM, replacing keep with persistent, and considering replacing nonfatal with fatal. I'd rather have a fail then an impossible slow client.
Xverify:none, deprecated and unsupported since Java 13. Suggest to NOT set it and let the JVM decide.
Xgcpolicy:gencon, the default. Suggest to NOT set it and let the JVM decide.
Xmaxt0.6, a rather generous allowance for time spent in gc. Suggest to NOT set it and let the JVM decide.
Looks like almost all of the parameters mentioned above were used for this KBase article:
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0113608