Hello Franz,
Thanks very much for you reply ... I have now amended the flow so that I have one master workflow with 3 sub-workflows (SLOW, MEDIUM,FAST). In each of the sub workflows there is only job (same job in each one using a different variable value).
Here are the results:
All jobs are using the max adaptive ERT with a tolerance of 10%
RUN 1:
FAST = 1
MEDIUM = 30
SLOW = 60
20180525/114531.187 - U00045021 Based on the feedback the ERT model for RunID '2508299' will be recalculated.
20180525/114654.391 - U00045018 Calculate estimated runtime for RunID '2508302'.
20180525/114654.406 - U00045019 The estimated runtime for RunID '2508302' is '30' seconds.
20180525/114654.609 - U00045018 Calculate estimated runtime for RunID '2508303'.
20180525/114654.609 - U00045019 The estimated runtime for RunID '2508303' is '61' seconds.
20180525/114654.812 - U00045018 Calculate estimated runtime for RunID '2508304'.
20180525/114654.812 - U00045019 The estimated runtime for RunID '2508304' is '2' seconds.
20180525/141148.838 - U00045020 Got feedback for the runtime estimation of RunID '2518183': estimated '2' seconds, actual runtime was '1' seconds.
20180525/141217.463 - U00045020 Got feedback for the runtime estimation of RunID '2518181': estimated '30' seconds, actual runtime was '31' seconds.
20180525/141247.666 - U00045020 Got feedback for the runtime estimation of RunID '2518182': estimated '61' seconds, actual runtime was '61' seconds.
All looks ok.
RUN 2:
FAST = 10
SLOW = 30
MEDIUM = 60
20180525/142401.355 - U00045021 Based on the feedback the ERT model for RunID '2516592' will be recalculated.
20180525/142432.199 - U00045018 Calculate estimated runtime for RunID '2516596'.
20180525/142432.199 - U00045019 The estimated runtime for RunID '2516596' is '33' seconds.
20180525/142432.386 - U00045018 Calculate estimated runtime for RunID '2516597'.
20180525/142432.386 - U00045019 The estimated runtime for RunID '2516597' is '61' seconds.
20180525/142432.527 - U00045018 Calculate estimated runtime for RunID '2516598'.
20180525/142432.527 - U00045019 The estimated runtime for RunID '2516598' is '2' seconds.
20180525/142442.949 - U00045020 Got feedback for the runtime estimation of RunID '2516598': estimated '2' seconds, actual runtime was '10' seconds.
20180525/142502.652 - U00045020 Got feedback for the runtime estimation of RunID '2516596': estimated '33' seconds, actual runtime was '30' seconds.
20180525/142532.933 - U00045020 Got feedback for the runtime estimation of RunID '2516597': estimated '61' seconds, actual runtime was '60' seconds.
FAST job is now taking 10 seconds and when estimated 2 but not reporting an overrun..
RUN 3:
FAST = 10
SLOW = 30
MEDIUM = 60
20180525/143710.809 - U00045021 Based on the feedback the ERT model for RunID '2517362' will be recalculated.
20180525/143741.731 - U00045018 Calculate estimated runtime for RunID '2514971'.
20180525/143741.731 - U00045019 The estimated runtime for RunID '2514971' is '11' seconds.
20180525/143741.888 - U00045018 Calculate estimated runtime for RunID '2514972'.
20180525/143741.888 - U00045019 The estimated runtime for RunID '2514972' is '60' seconds.
20180525/143742.060 - U00045018 Calculate estimated runtime for RunID '2514973'.
20180525/143742.060 - U00045019 The estimated runtime for RunID '2514973' is '10' seconds.
20180525/143752.482 - U00045020 Got feedback for the runtime estimation of RunID '2514973': estimated '10' seconds, actual runtime was '11' seconds.
20180525/143812.153 - U00045020 Got feedback for the runtime estimation of RunID '2514971': estimated '11' seconds, actual runtime was '31' seconds.
20180525/143842.341 - U00045020 Got feedback for the runtime estimation of RunID '2514972': estimated '60' seconds, actual runtime was '61' seconds.
Looks like it has changed the estimate of the FAST one correctly but also change the MEDIUM estimate to 11 seconds .. which now throws the overrun exception?
For information this is being run on .. Automic Web Interface 12.0.0.HF03-346
What we are trying to achieve is this:
We have one master workflow that will run against different environments (ENV1 and ENV2).
Within the master workflow we have sub workflows that will run the same job against separate data sets (SET1, SET2, SET3).
So I guess what we would like the ERT to take into account is the environment/data set the job is running against. e.g JOB1 needs to have its own estimate calculated for the combinations:
Environment | Data Set |
ENV1 | SET1 |
ENV1 | SET2 |
ENV1 | SET3 |
ENV2 | SET1 |
ENV2 | SET2 |
ENV2 | SET3 |
Also when we first execute this job in a LIVE environment I am guessing the adaptive ERT will be inaccurate/not there due to lack of previous runs/data? How do we handle this as we do not want overrun alerts being sent out without reason?
And another thing ... there will be certain jobs that throughout the month will take seconds to run and then for example on the last Friday of the month will take an hour...
If this is all achievable please can you let us know what settings we need to set and anything else we need to do?
Hope all this makes sense.
Cheers,
Dan