Nicolas Alvarez <nic### [at] gmailisthebestcom> wrote:

> I offered him my renderfarm, but his input data is way too big to
> transfer over Internet.

That's unfortunate because his simulations always leave me wanting that extra
few seconds.  My solution for now is that I think I will set up a script:
Crunch-parse-render-repeat.  Something like a screensaver.  Right now I run out
of space long before I run out of time.  It took ~10-15 hours to accumulate 80GB
of data, although that's the full double-precision velocity field.  I'd be
willing to run something on my home computer, but at 384 MB RAM and 867 MHz, I
don't know how far it would get.  Perhaps if the renderfarm were used for both
calculating and rendering, only an occasional restart file and images would
need to be transfered.  Not that I'm offering your resources, of course.
Excellent work though.  It'd be a shame for it to go unrendered.

 - Ricky

Post a reply to this message

wow!

hey, that place is from JVP's scenes, isn't it?  flooded... :)

so, a core 2 quad, huh?  That explains you interest in implementing path tracing
in povray and the relatively fast render times of the tests.  If I had this much
power in my hands, I too would like to see the CPU sweating -- all 4 cores! :)

Post a reply to this message

> To ask the obvious, isn't animation-rendering embarrassingly parallel?  Can't
> you just render four frames at a time?  I just finished parsing and rendering
> about 80+ GB of data on a Q6600 last night.  Just split up the files into three
> directories. and ran them separately.
When I can't use PovRay 3.7, I do the same : 4 instance of MegaPov running at
the same time (but in the same directory). I divide the frame range in 4 and
start the 4 renderings at 4 different positions.

Fidos

Post a reply to this message

"nemesis" <nam### [at] gmailcom> wrote:
> hey, that place is from JVP's scenes, isn't it?  flooded... :)
You are right, I gave credit in this post :
http://news.povray.org/web.4764e52fc1d3aa61423caea0%40news.povray.org

> so, a core 2 quad, huh?  That explains you interest in implementing path tracing
> in povray and the relatively fast render times of the tests.  If I had this much
> power in my hands, I too would like to see the CPU sweating -- all 4 cores! :)
It's clear that without 4 cores, I wouldn't start to play with path tracing !

Post a reply to this message