There are cases where TSTool slows down appreciably, usually when running memory-intensive workflows. In some cases, the solution is to increase the startup -Xmx option to allow more memory. For 64-bit Java, the limitation is machine memory, whereas with 32-bit Java the limitation is the JVM limit, typically around 64GB.
Ideally TSTool could monitor memory and perhaps garbage collection activity and recommend a change in configuration. Maybe add a command that tracks memory as each command starts and ends. There is already a ProfileCommands command so maybe need to improve that or implement some default profiling and warn the user regardless of whether ProfileCommands is used.
Subject of the issue
There are cases where TSTool slows down appreciably, usually when running memory-intensive workflows. In some cases, the solution is to increase the startup
-Xmxoption to allow more memory. For 64-bit Java, the limitation is machine memory, whereas with 32-bit Java the limitation is the JVM limit, typically around 64GB.Ideally TSTool could monitor memory and perhaps garbage collection activity and recommend a change in configuration. Maybe add a command that tracks memory as each command starts and ends. There is already a
ProfileCommandscommand so maybe need to improve that or implement some default profiling and warn the user regardless of whetherProfileCommandsis used.Environment
Steps to reproduce
Run a large command file.
Expected Behavior
Should run fast.
Actual Behavior
Runs slow and may run out of heap memory.