Graphics Reference
In-Depth Information
For large scenes, the process of packaging and uploading your file can take time, during which Blender can
seem to be frozen. Be patient. If all goes smoothly, your job will be submitted to the queue. If things don't go
smoothly, don't hesitate to report your problems to the Renderfarm.fi developers. Bug reports are always wel-
come.
Monitoring Your Progress
You can see how things are going from your account in Renderfarm.fi. Each job you've submitted will show up
on your account page, and its place in the queue for rendering will be shown on the Status page of the website.
Jobs are briefly inspected by hand before being sent to the render farm; depending on how busy the site admin-
istrators are, your job could spend some time in the queue before being sent to the farm. This is all factored
into the total time on Renderfarm.fi reported on the job page.
Figure 4-38
shows the graph for CPU use for a
nearly completed render job consisting of 150 frames 4096 by 2304 pixels in size, rendered at 2000 samples
with Cycles.
Notice that the actual rendering time of 5 days 19 hours is shorter than the total time spent on Renderfarm.fi
by about 8 hours. This is the amount of time this job spent on the queue. The top bar of the graph, in light
orange, indicates an estimated amount of time the job would have taken on a single CPU core. If this is shorter
than the second bar, then you aren't getting any improvement by rendering on the render farm (although you
might be freeing up your own computer to use for other things). In this example, though, you can see that the
job is moving nearly 16 times faster than it would have on a single CPU.
