Le 08/10/2014 13:25, CAD-Andi a écrit :
> I have the same issue with parsing large mesh files.

If you are using mesh{} (as opposed to mesh2{} syntax), this is
"normal": while parsing each additional vector (normal, vertex and so
on) of a mesh(), the parser perform a search on already parsed elements
of same kind.
For 1 million elements, that means 1 million search over an average of
half-million... can be very slow near the end.

Mesh2 syntax is optimised, but harder: it assumed the lookup as already
been done by the user. It is faster (really faster) on large mesh.

> I ease the pain by running
> multiple render tasks in parallel via separate render tasks (Povray instances)on
> Windows and multiple simultaneous logged in users on Mac OSX. Parsing can only
> utelize single core, but if you have many cores at your disposal you can chop up
> your animation into many render jobs and run them in paralell. With this method
> you utelize 100% of computing power out of your machine, even while parsing. If
> you use only one render task only one core will be busy while parsing.

-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message