|
![](/i/fill.gif) |
"Rafal 'Raf256' Maj" <raf### [at] raf256 com> wrote in
news:Xns### [at] 204 213 191 226
> CPU-1 render lines 0..160
> CPU-2 render lines 160..320
renders can be run as completly separate thread's (like running 2 copys of
POV at once, each on diffrent CPU). Disadvantage is duplicating memory, and
dual parsing for each process.
Second solution is :
Parsing scene - only one CPU
Shooting photons - one CPU,
or give 1-st, 3,5 light-source to 1-CPU and
2,3,6 to 2-CPU, and/or do same with target objects
Sorting Photons - there probably are algorithms for sorting on 2-CPU's
Radiosity pre-trace - not shure, maybe divide scene into separate pixels,
as in Render step
Render - give half pixels to one CPU, and half to others, run both
renders as separate threads tahat will share memory with
Photons/Vista/Scene/etc data
--
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M
Post a reply to this message
|
![](/i/fill.gif) |