The only time I've ever seen GE itself consume a significant amount of resources is when the reporting log is on and you're trying to push through thousands of jobs per second. The reporting log is of marginal value for us so I just turned it off. The accounting log is still a bit of disk load but it's useful enough that I left it on.
I don't think there's any practical upper limit to the number of nodes you want in a queue or in the cluster as a whole. It's really up to the tasks you're trying to run, and the policies/SLAs you've set for the cluster. On Thu, Sep 24, 2015 at 10:04:06PM +0000, Lane, William wrote: > If a cluster is running on a relatively slow speed networking backbone (say > gigabit ethernet or > 10 Gib ethernet as opposed to inifiniband), is there any commonly accepted > point at which increasing the number > of nodes in a queue negatively affects the performance of the queue? Is there > any general > rule about how many nodes to have in a queue based on a given network > backbone? -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
