#R3 Network Rendering
Greg (made of money) Pyros,
>> I couldn't live with less than 10
Of course it would depend on your thruput requirements, but I was
assuming a basic system to service one animator. Its an interesting
questions though .. eh?
OK .. maybe its between 4-8 machines .. We'll ( oh boy .. here comes
that engineering degree peaking out its ugly head) what we really
have here is a systems design and analysis problem.
Assume that one animator's average task takes 3 days to design. A 3
day design job probably equates to about a 30 second animation (on
average of course) so that's appoximately 1000 frames (keep the math
easy). Also, lets assume that each frame takes 5 minuites to render
.. so that's 5000 minuites .. or about 100 hours .. or about 4
days. Now, ofcourse one would want to be able to render the
animaiton and have something to look at that same day. In the above
case that would mean having _atleast_ 20 machines .. each rendering
for 5 hours each. Now if one can't afford that level of performance
.. then the job will have to render overnight .. so we can shoot for
a 18-24 hour turn around … which means 4-5 machines.
Therefore, I was wrong, there are 2 optimum setups. The first is
greater that 20 machines which would provide you with less than 1 day
performance or a setup of 5 machines … 4 rendering machines able to
turn the average animaiton around in less than 1 day of rendering and
one machine for constant design work (and turned into a renderer in
the evenings).
.. now my brain hurts… <g>