[rescue] using blender alone is going to be painful

[Shawn Wallbridge]

>From their page....

"Multithreaded rendering: use multiple CPUs to render a single frame without
incurring an increase in memory use."

We went with Dual Athlon's instead of singles just because the threading was
so good (that and licensing two CPU's is the same cost as one).

shawn

-----Original Message-----
From: rescue-admin at sunhelp.org [mailto:rescue-admin at sunhelp.org]On
Behalf Of Joshua D Boyd
Sent: Wednesday, February 27, 2002 12:02 PM
To: rescue at sunhelp.org
Subject: Re: [rescue] using blender alone is going to be painful


On Wed, Feb 27, 2002 at 11:25:46AM -0600, Shawn Wallbridge wrote:
> The new renderer that we are moving to (Exluna's Entropy) is heavily
> multithreaded. When we run it on our 8way, it pegs all the processors. It
> really flies on our new Dual 1.5GHz Athlon render slaves. We are very
> impressed with Entropy, it is really nice. The developers are great to
deal
> with and we have had very good output from it. We just bought 60 seats
> actually.

Is Entropy actually threaded, do does it just automatically spawn more
instances of itself?  I haven't used it, but I don't really see much reason
to bother with threads and network message passing in the same program.  If
you get much performance, then it means your platform has a fubared socket
system.

--
Joshua D. Boyd