...
- The disk where the server is running is is slow.
- The number of includes in the .ecf may be excessive, causing very large job files.
- Preprocessing takes to long. (i.e. replacing %VAR% in the .ecf file, with variables in the Node tree), removing comments and manual sections, etc.
- Server The server may be running out memory.
- The server is starved out of CPU time, competing with other processprocesses.
When the ecflow server is started, the ECF_TASK_THRESHOLD is read from the environment.
Job creation taking longer than this threshold are is written as a warning in the log file. The default threshold is 4000 milliseconds seconds.
However, in most cases this was ignored by the user , until some other problem arises.
In ecflow 5 series, they will be notified in the GUI that the the task has exceeded this threshold, by a new icon. This will allow early diagnoses of a looming problem.
...