...
- High disk latencies (i.e Check pointing takes a lot of time, or job processing take to long. Typically happens when using virtual machines, with non local data)
- very large scripts ( i.e in the megabytes), this can inflate the server memory, and cause job processing to take longer.
- Extremely large definitions, which are requested by many users, via the GUI. ( The download size, can be reduced, by only requesting the suite you are interested in)
- Very busy machine , where the and/or not enough memory available. ( i.e. server is competing for the resources, and where server is overloaded.)
- Server is overloaded. ( this can be visualised if you have gnuplot installed, and available on $PATH, i.e invoke ecflow_client --server_load=<path to the log file> )
To diagnose these cases, we need to look at the log file. Typically you will see two or more child commands (--init/complete), where the second will then be treated as a zombie.
...