The thing is we got about 30 scenes that need to render out frames (about 2K
resolution) for printing purposes, and those take a long time to render out
on a dual xeon machine (about 9 hours per frame). This is why we need to get
them rendering in a distributed render.
Daniel
-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of
kim aldis
Sent: Thursday, October 27, 2005 3:32 PM
To: XSI(at)Softimage.COM
Subject: RE: Distributed Rendering Crashing XSI
Exactly. You can plot a graph and watch how the actual frame times go up for
a while as you add machines then start to drop. I think I worked out you can
actually get to a point where frames render slower than if you were
rendering on a single machine.
There's a place for short runs or single frames of extreme complexity,
though
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM
> [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Stefan Andersson
> Sent: 27-October-2005 13:48
> To: XSI(at)Softimage.COM
> Subject: Re: Distributed Rendering Crashing XSI
>
> Personally I think satellite rendering doens't work at
> all.... too much network loads and it can make the renderings
> go slower instead of faster. So, I would recommend a purchase
> of a few XSI Batch nodes (standalone). If you are only using
> XSI and not any other 3D software that uses mental ray (or
> use mi files for rendering) you don't need the "Batch Universal".
>
> Just a thought... the number of days you will spend on trying
> to get it to work will cost you more than actually buying to
> rendernodes :)
>
> regards
> stefan andersson
>
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following
> text in body:
> unsubscribe xsi
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
