[Swift-user] passive worker job assignments

Allan Espinosa aespinosa at cs.uchicago.edu
Mon Oct 4 12:58:37 CDT 2010


No, I meant how many will it queue to that specific worker.  By
default I know it is some factor of workersPerNode * Overallocation.

2010/10/4 Michael Wilde <wilde at mcs.anl.gov>:
> Do you mean "how many jobs will each worker run concurrently"? I think that is workersPerNode, which is still in effect in passive mode as far as I know.
>
> So I would think you start one worker per compute node, and workersPerNode (which should really be renamed concurrentJobsPerWorker) determines how many jobs each worker will concurrently launch.
>
> Thats my understanding; Mihael and Justin should correct or confirm this.
>
> - Mike
>
>
> ----- "Allan Espinosa" <aespinosa at cs.uchicago.edu> wrote:
>
>> Hi,
>>
>> When coasters are in passive mode, how many jobs are assigned to the
>> workers?  Is it still decided by the *Overallocation parameters?
>>
>> Thanks,
>> -Allan



More information about the Swift-user mailing list