gpt.sh use the same Graph Processing Framework (GPF) libraries, so "Proper Parameters Prevent PXXX Poor Performance". Java memory allocation is a tricky topic, but for starters, you should compare the values of the "-Xmx" option used by the SeaDAS 7 GUI from seadas.vmoptions with the value in your . On a system used for small teaching examples: % grep Xmx seadas.vmoptions gpt.sh
seadas.vmoptions:# -Xmx512m
seadas.vmoptions:-Xmx1024M
gpt.sh: -Xmx1024M \
Here, the hash (
#) indicates a line that has been commented out. These can be considered starting values. If you encounter performance problems, try doubling the values until performance is acceptable without exceeding 60% of the system memory. If your system has minimal RAM (4GB for linux) you may need to add RAM. Reducing the size of your level-2 files will lower memory demands for GPF processing. If your
gpt.sh script already has the same setting as your GUI, you may be attempting to use more memory than is installed on the system. Linux can use swapping to temporarily stores areas of memory to disk, but this is very slow. On lower spec machines you may not be able to use the GUI and gpt.sh efficiently at the same time. There are many tools that can be used to monitor system memory usage. You can use the free command in a terminal window:$ free -m
total used free shared buff/cache available
Mem: 6256 63 3344 0 2849 5906
Swap: 2048 0 2048Consult the references for your distribution for GUI tools.
