|
![](/i/fill.gif) |
In article <40577bfc@news.povray.org>, Warp <war### [at] tag povray org>
wrote:
> However, if you make code which calculates something without creating
> objects, then quite obviously memory allocation is not an issue there.
Unless the memory allocation is actually lots of small chunks of memory
that are quickly freed again...small temporary structures for values
during expression parsing, for example. In a loop, it may create a new
variable structure for every update of the loop counter, causing extra
memory allocations.
Anyway, the slowness certainly is due to more than memory allocation,
and switching to a VM certainly would speed things up. Memory allocation
does account for a big chunk of the parse time, though...scenes can
consist of many megabytes of small structures, and allocating all of
these takes time. Maybe do something to handle structures that will last
the entire render differently from those that are short term.
--
Christopher James Huff <cja### [at] earthlink net>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tag povray org>
http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |