File: limit-submission.rst

package info (click to toggle)
ecflow 5.15.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 51,868 kB
  • sloc: cpp: 269,341; python: 22,756; sh: 3,609; perl: 770; xml: 333; f90: 204; ansic: 141; makefile: 70
file content (64 lines) | stat: -rw-r--r-- 2,243 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
.. index::
   single: limit (tutorial)

.. _tutorial-limit-submission:

Limit (Task Submission)
=======================

The previous section has shown how ecFlow provides simple load management.

Even when using limits, it is still possible to allow several hundred jobs to be submitted at once, which can cause problems:

- Excessive disk/io in job generation
- Server busy in job generation, and slow to respond to the GUI.
- Overload queuing systems like PBS/SLURM

To avoid these issues, limits can also be used to restrict the number of submissions, and in this case, when the Job becomes active the limit token is released.

The following shows the use of :code:`inlimit -s` option, which helps to control the number of tasks in the submitted state.
There can be **more than** 2 active jobs, since **only** the number in the submitted state is controlled.
The removal of the :code:`-s` option would mean that only two active jobs would be allows to execute in parallel.
The use of the :code:`-s`  allows the configuration of the suite, depending on the load the disk/io and queuing system can sustain.

The following is a simple illustration that modifies the previous example.

.. tabs::

    .. tab:: Text

        Modify the :term:`suite definition` file, as follows:

        .. code-block:: shell

           # Definition of the suite test.
           suite test
            edit ECF_INCLUDE "$HOME/course"
            edit ECF_HOME    "$HOME/course"
            limit l1 2
            family f5
                inlimit -s l1 # by default consume 1 token from the limit l1
                edit SLEEP 20
                task t1
                task t2
                task t3
                task t4
                task t5
                task t6
                task t7
                task t8
                task t9
            endfamily
           endsuite

    .. tab:: Python

        .. literalinclude:: src/limit-submission.py
           :language: python
           :caption: $HOME/course/test.py

**What to do**

#. Apply the changes to :term:`suite definition`.
#. In :term:`ecflow_ui`, observe the effects on the number of submitted tasks.
#. Change the value of the :term:`limit` and inlimit, and observe the effects.