OPENDJ-5963 calls for updating recommendations in the documentation regarding JVM options.
A more user-friendly solution consists in updating the setup command to implement the recommendations based on the JVM used during the setup process, and then updating the documentation to reflect the change.
The setup command could determine the JVM characteristics, such as version and OS data model architecture (32- or 64-bit), and record the JVM and recommended settings in java.properties.
As this would not help people who set OPENDJ_JAVA_ARGS, the setup command could also display information about the settings, such as the fact that they are set in config/java.properties and that the equivalent OPENDJ_JAVA_ARGS for start-ds would be OPENDJ_JAVA_ARGS=-XX...y...z, etc.
At present, the user setting up the server would have to indicate how much memory to devote to DS (or default to the JVM default setting). If the proposed RFE to cache only internal nodes is implemented, this choice could reasonably be dropped from the setup questions: users would more likely run out of file system cache than heap for inner nodes.
The install documentation should then tell users to employ the same JVM to set up and run the server and tools. When setting up in a different environment, users could edit default.java-home in config/java.properties. Users requiring different settings in different environments (e.g. different memory settings for dev, QA, and prod) could also choose to modify the OPENDJ_JAVA_ARGS settings, starting with the recommended settings displayed by the setup command.