 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
http://www.par4all.org/
anyone in for trying it with povray to see what happens? :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
nemesis wrote:
> http://www.par4all.org/
>
> anyone in for trying it with povray to see what happens? :)
Isn't the latest POV-Ray beta *already* parallel?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible <voi### [at] dev null> wrote:
> nemesis wrote:
> > http://www.par4all.org/
> >
> > anyone in for trying it with povray to see what happens? :)
>
> Isn't the latest POV-Ray beta *already* parallel?
only for multicore CPUs, not heterogeneous computing environments including GPUs
and clusters...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Isn't the latest POV-Ray beta *already* parallel?
>
> only for multicore CPUs, not heterogeneous computing environments including GPUs
> and clusters...
Now I know for a fact that Debian won't let you install POV-Ray until
you install PVM, so I'm guessing "clusters" have already been done.
Targetting the GPU would be another matter, given the flow-control issues.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/27/2010 5:21 PM, nemesis wrote:
>
> only for multicore CPUs, not heterogeneous computing environments including GPUs
> and clusters...
>
My understanding of the structure of 3.7 is that this should be
possible, even trivial to configure the application up for clusters. The
rendering is done on the back-end for each tile, each tile reports back
to a controller. The controller gathers image data and statistics from
the renderer and sends new tiles to idle threads.
Of course, I may be totally wrong (and I frequently am...)
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford wrote:
> My understanding of the structure of 3.7 is that this should be
> possible, even trivial to configure the application up for clusters.
>
> Of course, I may be totally wrong (and I frequently am...)
Pah, *everything* is trivial for the person who isn't trying to
implement it. ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/30/2010 8:15 AM, Invisible wrote:
> Pah, *everything* is trivial for the person who isn't trying to
> implement it. ;-)
Absolutely! :)
--
~Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ok, perhaps a better goal was to feed it the sources of povray 3.5 to see if it
would compete with 3.6 right now. :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 30.07.2010 15:08, schrieb Mike Raiford:
> My understanding of the structure of 3.7 is that this should be
> possible, even trivial to configure the application up for clusters. The
> rendering is done on the back-end for each tile, each tile reports back
> to a controller. The controller gathers image data and statistics from
> the renderer and sends new tiles to idle threads.
That's the idea behind it, yes.
However, we're not there yet - cluster rendering support, while being on
the roadmap, is not on the agenda for 3.7; there's still a lot of data
simply shared among the threads rather than being passed around by
messages, and that won't be addressed until after the 3.7 release proper.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
