From: Daniel Browne <dbrowne@(email surpressed)>
Subject: Re: Restricting User CPU's
   Date: Tue, 15 Feb 2011 16:44:08 -0500
Msg# 2016
View Complete Thread (12 articles) | All Threads
Last Next
Rush CPU's, yes; I'd like make it so that no matter how many jobs an artist has sitting in the queue, he or she can utilize only a maximum of say 10 render machines at any given time.


On Feb 14, 2011, at 7:41 PM, Greg Ercolano wrote:

[posted to rush.general]

Daniel Browne wrote:
> [posted to rush.general]
> 
> Does anyone know of a way to restrict the maximum number of cpus that a use=
> r may have running jobs at any given time?

	Do you mean 'rush cpus' (ie. how many instances of rush renders),
	or 'physical cpus'?

	Rush cpus can be controlled in several ways; the 'CPUS' column in the
	rush/etc/hosts file, the Ram: value when a user submits, 'rush -reserve'.

	Physical cpus can be limited on windows machines using "processor affinity"
	in the rush/etc/hosts file, eg:
	http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1899+1898+1899+1900+1905
	The 102.42a9c version of rush supports this for windows only,
	the next release of rush will also support it for linux.
	AFAIK, OSX's kernel does not yet support processor affinity.


-- 
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)

----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures

dbrowne@(email surpressed)
Office: (415) 777-0666 x105


Last Next