[Swift-user] Coaster jobs are not running with expected parallelism

Mihael Hategan hategan at mcs.anl.gov
Tue Jan 19 13:44:06 CST 2010


On Tue, 2010-01-19 at 13:38 -0600, Michael Wilde wrote:
> 
> On 1/19/10 1:32 PM, Mihael Hategan wrote:
> > Maybe PBS is lying about that 18 node job. 
> 
> I would be surprised if thats the case. But even if it had *1* node you 
> would think it would run at least 8 jobs in parallel.

I see. Though not with your current setup. You should use
"workersPerNode" instead of "coastersPerNode".

> 
> Im confused why it has started three jobs, two with only one core and 
> one with 18 nodes.

It does that. It spreads out the block sizes to exploit non-linearities
in queuing times.

> 
> But the 18 node job just hit its wall time limit; now coasters seems to 
> have started a 10 node job:

Don't know about that. Logs please.





More information about the Swift-user mailing list