...
The clientConfig.xml file can be used for memory allocation (RAM) and disk space allocation for local cache files. Memory The default memory setting is 1024m. Increased memory allocation settings are added to the jvMOptionsneed to be configured using <jvmOption></jvmOption> elements.
| Code Block |
|---|
<jvmOption>-Xms1024m</jvmOption> <jvmOption>-Xmx2048m</jvmOption> |
...
When rolling out a Delft-FEWS application, it is best practice is to test the application with a low memory setting (e.g. 1024Mb) and perform some performance tests with intensive viewing of grids first. If the application's performance becomes sluggish when using a low -Xmx setting, it is likely that the Java garbage collection memory management process is responsible. In that case it is time to tune to a higher -Xmx setting. For testing a configuration with 64 bit Java (from FEWS 2018.02), -Xmx1500m is a good starting point, but -Xmx2048m is most also commonly used, higher numbers can be used if necessary. The final rolled out Delft-FEWS application should be able to run smoothly with the specified -Xmx value.
...
The tooltip on the FEWS Explorer memory element will also provides information on memory usage.
...