Hi there
We sometimes encounter a problem where slow jobs containing frames
that consistently exceed the maxtime for the job are tying up the farm
overnight when other jobs could be going through. We've tried to
address this by adding some checks to the render script whereby if
more than say five frames in a job failed due to exceeding the maxtime
the job would be paused. Unfortunately however it looks like jobs
that exceed their maxtime are killed immediately by rush, without the
render script having a chance to respond to the event, and without
anything being (consistently) output to the log which we can use to
detect that the maxtime has been exceeded.
One of our artists ran a test job through the farm, and we noted that
the following message seemed to be generated for the first failed
frame only, subsequent frames contained no such information in the logs:
--- KILLED: MAXTIME EXCEEDED 00:01:00
We were hoping to find out if there was a simple way for our render
script to determine if maxtime has been exceeded for a frame?
Nothing obvious seems to stand out in the docs.
Regards
--
Dylan Penhale
IT Manager
Fuel International
65 King Street
Newtown
Sydney
Australia 2042
p. (Tel# suppressed)
f. (Tel# suppressed)
m. +61424 655 320
w. www.fuelvfx.com
|