So for the first 500 or so frames of an animation, our render times were between 7-10 minutes. Then sporadically, it keep rending other frames that we’ve had to re-queue after they’ve spent about 2 hours sitting there. For instance, 512 will show as rendered 7:45, then 513 hangs, then 514 renders in 8:30.
I just started the Automatic Job Timeout, so not sure if it has to be on before submitting a project or if it can be turned on after a project has rendered frames. Will it average all the previous frames to determine the best time to Auto-timeout? The reason I ask is because after I turned it on, it doesn’t seem to be respecting it because render time are going past 140%
It’s a max 2014 design scene, vray 3.0, DL 6.1.
-Chip
Hey Chip,
I’m not an expert with the automatic timeout mechanism yet, but it is supposed to take an average, then allow for that configurable percentage before quitting the task. I would assume the Slave would do it during it’s regular pings to the database every seven seconds so you wouldn’t need to re-submit the job. I’ll need to ask Ryan the exact details so I can comment better.
So, turns out my understanding here is flawed. It will take the longest running completed task and use that for its base, so if there is another task that took an hour, it could push things even further.
Normally, you would see at worse a steadily increasing list of tasks, but since the job had started after you enabled things that would explain it.