[Swift-devel] Expected behavior for scheduler slow-start with coasters?

[Michael Wilde]

OK, this one seems to be more of a nuisance/anomaly that we can set 
aside for now I think.

Opening up the throttle a bit should make this a minor issue. 
Eventually, you'd hope it would fill available coasters when there is 
demand, or at least base the rampup on the fast that jobs started, and 
not wait for them to finish. Then it would sense faster that there were 
more ready workers.

On 4/6/09 5:08 PM, Mihael Hategan wrote:
> On Mon, 2009-04-06 at 17:00 -0500, Michael Wilde wrote:
>> We are seeing the following on Ranger:
>>
>> Swift has 2 coaster jobs running in SGE, coastersPerNode is set to 16, 
>> yet it seems to be doing "slow start" as if it doesnt know that it ca 
>> quickly fill the available coaster slots.
> 
> Right. Swift doing a slow start is a given.
> 
> Coasters allocating more workers than needed is the issue.
> 
>