[Swift-devel] burnin' up ranger w/the latest coasters

[Mihael Hategan]

On Fri, 2009-10-23 at 13:02 -0500, skenny at uchicago.edu wrote:
> >> however...when i use the configs here and i try to run a
> >> workflow with 196,608 jobs it seems that coasters starts to
> >> ramp up nicely, but maybe a little too well :) as it begins
> >> requesting more cores than i'm allowed in the normal queue on
> >> ranger. that is, the limit is 4096. i tried changing maxNodes
> >> to 4096 which did not work.
> >
> >Shouldn't that be 4096/workersPerNode?
> 
> don't think i'm understanding you here...the workersPerNode
> you originally suggested was 32. why would i increase that to
> 4096 when what i'm trying to do is request fewer total cores? 

No.
If you have C CORESPerNODE and the maximum number of CORES you can
request is 4096, then the maximum NODES you can request is 4096/C not
4096.

You are setting maxNodes to 4096. That means it will request 4096*16
cores.