HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Add a new idea Subscribe
Status Needs Review
Workspace Notes
Created by Guest
Created on Mar 19, 2024

RELATED IDEAS

Update jvm.properties to Java 17 standards

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.

I referred to https://eclipse.dev/openj9/docs for reference.

Suggestions:

  1. 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.

  2. Xms: to high, an early gc forcing out boot only structures promotes health. Suggest 128m

  3. Dosgiext => underlying log framework needs fix for change very very long time ago

  4. 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.

  5. Xmaxaot12m, very old max. Suggest to NOT set it and let the JVM decide.

  6. Xminf0.1, old. Suggest to NOT set it and let the JVM decide.

  7. Xmn7m, very old. Hampers proper nursery. Suggest to NOT set it and let the JVM decide.

  8. 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.

  9. Xverify:none, deprecated and unsupported since Java 13. Suggest to NOT set it and let the JVM decide.

  10. Xgcpolicy:gencon, the default. Suggest to NOT set it and let the JVM decide.

  11. Xmaxt0.6, a rather generous allowance for time spent in gc. Suggest to NOT set it and let the JVM decide.

  • Attach files
Copyright © 2023 HCL Technologies Limited