how to sleep 1 between two runICRP when ADE submit to LSF

I'm not aware of a way of doing this as a standard feature, but one way could be to use command mode and make the command:

randSleep ; bsub ...

The randSleep being this script below (you could also use randSleep 20 if you want a larger maximum sleep). 

#!/bin/sh
# sleep by a random interval - up to a maximum passed
# to the script, or 10 if no arguments.
if [ $# -lt 1 ]; then
  maxDelay=10
else
  maxDelay=$1
fi
sleep $(($RANDOM % $maxDelay))

I'm not convinced this is a good idea though! Maybe only use it when you have a job policy where you are submitting lots of jobs.

Andrew

Hi andrew,

Thanks your firstly.

I rename the script called as sleep.bash.

cat sleep.bash:

#!/bin/bash

sleep $(($RANDOM % 5))

and then submit 4 runICRP to LSF using Command mode='/xxx/sleep.bash; bsub ....' in job policy, 

and then run bjobs, it looks like:

Wed Jul 27 00:47:47: Submitted from host <h1>, CWD </xxx
Wed Jul 27 00:47:47: Submitted from host <h2>, CWD </xx
Wed Jul 27 00:47:48: Submitted from host <h3>, CWD </xx
Wed Jul 27 00:47:50: Submitted from host <h4>, CWD </xx

yes, we can see some jobs submitted time has a delay. 

but  job1 and job2 submit time is still the same,  job3 and job4 has a sleep 2.

I know it is caused by $RANDOM % 5.

so one more question,

how to optimize this script in order to control exactly only 1 second dealy  between every runICRP?

Thanks

zsummer said:

how to optimize this script in order to control exactly only 1 second dealy  between every runICRP?

If I'd thought of a way of doing that (since that's what you'd originally asked), I'd have done it. Having the script read and write a file which increases by a second each time would be a very bad idea because it would just keep increasing and at some point you'd want it to reset. It would be better to have the system which submits the command wait for a second before each subsequent submission. I don't think there's a way of doing that (at least I'm not aware of a way) - so you should contact customer support.

Andrew

Actually, there's going to be a new cdsenv variable in IC6.1.8-64b.500.27 (ISR27) due out later this month which does this:

maestro.lscs	 minimumJobSubmissionInterval int 0

I believe it will also affect ICRP. The default is 0, but can be increased - the value is the number of seconds between job submissions.

Andrew