[EMAIL PROTECTED] schrieb am 05/28/2008 05:43:08 AM: > > On May 27, 2008, at 12:20 AM, Yuriy wrote: > > > We have 10 node cluster with 2 > > quad-core processors per node, and when number of jobs is greater then > > 160 > > > Why are you treating globus job submissions like an extended batch > queue?
... > Anyone want to chime in? I would say that treating Globus job submissions like an extended batch queue should be among the allowable use cases. Users of a local batch scheduler may view the "Grid" as a drop-in replacement, which they expect to be at least as easy to use and efficient, just more fault-tolerant and scalable. The fewer gotchas, incompatibilities, weird issues, and technical workarounds they must care about, the better. It's hard enough to convince them to abandon their familiar client software. So if Globus consumes system resources even for idle jobs, then it seems to me like a design or implementation flaw in Globus, not a user's misunderstanding. (I believe it is no longer so bad in GT 4 as it used to be in the earlier versions. Your remarks about the need for client-side submission throttling are of course correct.) Regards, Jan Ploski
