Oct 2, 2020

    RushTI optimized mode

    RushTI now has an alternative execution mode: OPT
    It allows for an optimized execution schedule.

    To use the new OPT mode, execute rushti like this:
    RushTI.py tasks.txt 2 opt

    With a tasks.txt file like this:

    id="1" predecessors="" instance="tm1srv01" process="}bedrock.server.wait" pWaitSec=1
    id="2" predecessors="1" instance="tm1srv02" process="}bedrock.server.wait" pWaitSec=2
    id="3" predecessors="1" instance="tm1srv01" process="}bedrock.server.wait" pWaitSec=3
    id="4" predecessors="1" instance="tm1srv02" process="}bedrock.server.wait" pWaitSec=4
    id="5" predecessors="2,3" instance="tm1srv01" process="}bedrock.server.wait" pWaitSec=5
    id="6" predecessors="4,5" instance="tm1srv02" process="}bedrock.server.wait" pWaitSec=6
    id="7" predecessors="4" instance="tm1srv01" process="}bedrock.server.wait" pWaitSec=7
    id="8" predecessors="6" instance="tm1srv02" process="}bedrock.server.wait" pWaitSec=8`

    When you have individual dependencies between your processes, but you want to use parallelization nonetheless, this can make quite a difference.

    The old execution mode is still the default mode, so if you don’t provide the OPT argument RushTI will assume you want to use the normal mode.

    Related content

    Loading related content