Ist there a programm or so forcing Povray to render big jobs on several PCs
(Windows NT) in a Network (somethig like a "render-farm")?

Post a reply to this message

Nowadays lotsa people are sharing data (Napster, KaZaA, Xolox, etcetera
etcetera). But what about cpu sharing? It would be neat if members of the
'povray community' with spare cpu time could form a 'rendering pool' or
something. In many cases this would really speed up renderings.

Anyone any ideas or information?

Post a reply to this message

http://www.imp.org

Apache wrote:

> Nowadays lotsa people are sharing data (Napster, KaZaA, Xolox, etcetera
> etcetera). But what about cpu sharing? It would be neat if members of the
> 'povray community' with spare cpu time could form a 'rendering pool' or
> something. In many cases this would really speed up renderings.
> 
> Anyone any ideas or information?

Post a reply to this message

Thanks! I just sent the people of IMP a request for more info.

I'm wondering about the technical background of IMP. Is it fully automated
or do I receive parts of the project by mail or something? If it would be
fully automated I could leave a computer running for weeks without
intervening and stuff.

Post a reply to this message

Apache wrote:
> 
> Thanks! I just sent the people of IMP a request for more info.
> 
> I'm wondering about the technical background of IMP. Is it fully automated
> or do I receive parts of the project by mail or something?

As far as I know it is all done through the internet via TCP/IP protocols.
There are "jobs" uploaded to the render queue at the IMP website. When
you fire up IMP-Pov and log on and it will check to see if any jobs are
waiting.

> If it would be
> fully automated I could leave a computer running for weeks without
> intervening and stuff.

Once you have it up and running it is fully automated as long as there
are render tasks left in the queue.  If you have an always on connection,
or an unlimited access dial up connection, you could theoretically render
for months on end.

Note that only individual frames are rendered. It will not split up
single frames across multiple computers.

-- 
Ken Tyler

Post a reply to this message

> Note that only individual frames are rendered. It will not split up
> single frames across multiple computers.

That perfect: no radiosity problems at this point!

Post a reply to this message

Just wondering,
what are the Radiosity problems with splitting a single frame across
mutliple machines?

"Apache" <apa### [at] yahoocom> wrote in message
news:3bfcf291$1@news.povray.org...
> > Note that only individual frames are rendered. It will not split up
> > single frames across multiple computers.
>
> That perfect: no radiosity problems at this point!
>
>

Post a reply to this message

On Wed, 28 Nov 2001 23:18:11 +1000, "Davin"
<dav### [at] itcmconsultcomau> wrote:

>Just wondering,
>what are the Radiosity problems with splitting a single frame across
>mutliple machines?

In brief, the radiosity samples are kept in a structure known as an
octree. The radiosity octree is created during pre-rendering and
rendering. Therefore the nodes have to somehow share the information
they add to the octree so that they use identical copies. Francois
Dispot has solved the problem, to a large extent, in PVM-MegaPOV and
can probably enlighten you more on the subject.


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

Use ... (see below).

--Theo

----------------------------------------------------------------------------
---------------------------------
Distributed Network-Rendering or Local SMP-Rendering on all CPU's you have.
With SMPOV und POV-Ray 3.5.Download free at:
http://www.it-berater.org/smpov.htm

Post a reply to this message