ecFlow's documentation is now on readthedocs!

Please go to https://ecflow.readthedocs.io/en/latest/index.html

  • Created by Unknown User (ma0), last modified on Jan 25, 2019

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

When job creation takes to long, ecflow server writes a message to the log file. It can be slow for a variety of reasons.

  • The disk where the server is running is really slow.
  • The number of includes in the .ecf may be excessive, causing where 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 may be running out memory.

When the ecflow server is started, the ECF_TASK_THRESHOLD is read form the environment. Job creation taking longer than this threshold are written as a warning in the log file.

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  task has exceeded this threshold, by a new icon.


  • No labels