[Swift-user] Tuning parameters of coaster execution

[Mihael Hategan]

On Tue, 2009-10-20 at 12:04 -0400, Andriy Fedorov wrote:
> On Tue, Oct 20, 2009 at 11:55, Mihael Hategan <hategan at mcs.anl.gov> wrote:
> > You need a more recent version of the code.
> >
> 
> Mihael, I actually updated svn for both cog and swift yesterday prior
> to running the tests. Here's what swift reports I have right now:
> 
> Swift svn swift-r3170 cog-r2529

Given that even when you have granularity=10 you still see 2 jobs, I
suspect you are using swift site throttling parameters that force that.
I would set the jobThrottle higher and possibly the initial score
higher.

For troubleshooting, what you could do is, on the remote side, say cat
~/.globus/coasters/coasters.log|grep "BlockQueueProcessor">bqp.log and
post that. Also, you could set the remoteMonitorEnabled profile to
"true" to get visual feedback of what's happening.

The allocation time is 18 minutes because the new stuff doesn't
overallocate using a fixed multiplier (though you can force it to do
so). For small jobs (walltime = 1s) the multiplier is set by
lowOverallocation (10.0 by default) while for large jobs (walltime ->
+inf) the multiplier is 1, with an exponential decay in-between.

If you want to always have blocks being 10 times the job walltime, you
can set highOverallocation to 10.