[Swift-devel] spread changing or lots of big jobs left behind

[Mihael Hategan]

On Tue, 2010-06-29 at 11:10 -0500, Allan Espinosa wrote:
> Based on the attached screenshot, swift now requested for 1036 nodes
> which is much greater than 198 of the maxnodes.

Maxnodes applies to one block.

I suppose there should be maxNodes and maxBlockNodes.

>  The swift session log
> reports 1450 jobs submitted.  I would have expected ~10360 jobs
> submitted since i use the default overallocation factor of 10.

The overallocation applies in time not in breadth.

> 
> During the first few hours/ minutes of the workflow, swift was still
> submitting small jobs (10~20 workers per slot) along with the large
> request.  Based on this observation, does swift request the entire
> spread per batch?

Each round of block allocation will consider the available slots and the
spread.

> 
> Also, how does jobThrottle now factor into submitted jobs and
> corresponding slots?

It's orthogonal. Swift will submit jobs as it normally would.