From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: Logging progress inside a command
   Date: Mon, 23 Oct 2006 16:06:24 -0400

Hugh Macdonald wrote:

[posted to rush.general]

Hi all,

I'm relatively new to Rush, having helped evaluate it for a previous company (we ended up deciding to stick with Alfred for the time being, which we had a lot of code based around), and am now working at a company that has recently started using Rush.

I've looked through the docs, and scanned the archives of the newsgroup for the answer to this question, but nobody seems to have brought it up, so I'm going to assume that I'm being a muppet and am missing something obvious. If you could tell me what I'm missing (in the nicest possible way), I'd be grateful.

At the moment, Rush will only give a Done % as each box finishes, but I'd like it to be able to pick up when, for example, a box is 50% done. Something that is easily parsable from the Shake output...

	Irush doesn't try to parse the continuous output of the renderers,
	though I suppose it could.

	I've seen a few requests for this before, and I might try to entertain
	adding it as a feature to rush if a see a clean technical path to
	implement it that doesn't suffer from scaling problems.

	Mainly it's an issue of scalability.. eg. if you start a rush job
	and it jumps on 50 machines, irush would have to parse the logs
	for realtime output of all 50 machines to update the report. Or worse,
	if there's 300 machines that start working on the job.

	Also, rush supports a lot of renderers.. many don't show percent
	completion messages, so it wouldn't be universally deployable.
	And finally some renders (mental ray) goes through the zero-to-100
	percent progress potentially several times, depending on how many
	passes it has.

	The current way to monitor progress in real time is to get an idea
	of the average time it takes frames to render (see the 'ELAPSED'
	times in the 'Frames' report, or the 'average render time' in the
	'Frames Info' report), and then put the Frames button on 'repeat'
	(Hit "REP", then hit "Frames"), and then monitor the ELAPSED times
	for the busy frames to see how fast things are going.

	Or, just keep the 'Frame Info' or 'Jobs' report on 'repeat' to
	keep an eye on one or several jobs at a time.


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