From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: job owner needs to be online?
   Date: Tue, 06 Mar 2012 13:41:43 -0500
Msg# 2196
View Complete Thread (4 articles) | All Threads
Last Next
On 03/06/12 10:32, Dan Rosen wrote:
> [posted to rush.general]
> 
> Are there any limitations to making one machine the Submit Host for many =
> jobs? Obviously jobdonecommands would be a factor, but outside of that, =
> are there any limitations for one machine acting as the Submit Host for =
> 100s of jobs?

	Depends only on how much the machine can handle.

	100's of jobs shouldn't be a problem.. it has more to do
	with how many render nodes you have all beating on this one
	box for frames to render for that many jobs.

	It should be able to scale to a few hundered jobs
	on a few hundred cpus for a single box.

	Depends on the renders though; if the renders are slow,
	it's less an issue. For really fast renders (a few seconds,
	like a comp), this puts more load on the job server, because
	it has to more quickly turn around frames.
	
	If you're concerned about load, I'd suggest more than
	one box for load balance. So if you have 30 users,
	perhaps break them up into two or three groups, assigning
	each group its own submit host.



-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)


Last Next