From: Dylan Penhale <dylan@(email surpressed).au>
Subject: very long elapsed times in Frames report 
   Date: Sun, 17 Sep 2006 21:41:48 -0400
Msg# 1381
View Complete Thread (2 articles) | All Threads
Last Next
We have just noticed some very long elapsed times when using the frames report 

e.g.
Done 0115 1 rufe.3d 1412 spitfire.749 09/18,08:23:37 00:27:21 Fail 0116 2 snoopy 10728 spitfire.749 09/18,09:15:41 1191853:36:24 Fail 0117 1 helldiver 1188 spitfire.749 09/18,08:24:23 01:00:09 Fail 0118 2 odie 5144 spitfire.749 09/18,09:18:23 1191853:33:43 Done 0119 1 lionheart 3920 spitfire.749 09/18,08:43:38 00:31:28 Done 0120 1 arrow.3d 3988 spitfire.749 09/18,08:48:56 00:26:33 Done 0121 1 fluffy 1416 spitfire.749 09/18,08:51:56 00:29:35 Done 0122 1 nate.3d 2536 spitfire.749 09/18,08:53:00 00:27:21 Done 0123 1 hustler.3d 796 spitfire.749 09/18,08:57:44 00:26:57 Done 0124 1 sabre.3d 1320 spitfire.749 09/18,08:57:53 00:27:11 Fail 0125 1 hooch 29076 spitfire.749 09/18,09:21:44 1191853:30:15
This plays havoc with the max times settings. Any ideas where to start looking for this? All machines are time synced regularly. 





Regards

Dylan Penhale
Systems Administrator
Fuel International
65 King Street
Newtown
2042
Sydney
Australia
p. (Tel# suppressed)
f. (Tel# suppressed)




   From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: very long elapsed times in Frames report
   Date: Mon, 18 Sep 2006 03:01:13 -0400
Msg# 1382
View Complete Thread (2 articles) | All Threads
Last Next 
Dylan Penhale wrote:
We have just noticed some very long elapsed times when using the frames report 

e.g.

Fail 0116        2   snoopy          10728   spitfire.749     09/18,09:15:41     1191853:36:24
Fail 0125        1   hooch           29076   spitfire.749     09/18,09:21:44     1191853:30:15
This plays havoc with the max times settings. Any ideas where to start looking for this? All machines are time synced regularly. 

	I'm pretty certain this is a windows specific problem.. I need to figure
	out the cause.

	Rush doesn't use normal time/date calls for the elapsed time calculations
	to avoid problems with changes in the date and time. eg. you can change
	the system clock's date and time without affecting the rush elapsed time
	indicators.

	Can you email me (directly) a zip'ed version of spitfire's
	rush/var/jobs-checkpoint file so I can see if I can trace this.

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