This is really very much depending on the scene.. 
Take the macros that made the gnarled tree..
on my pc, 3 trees at recursion level 5(I think) took around 1 min 40 sec to parse,
while
the same files, though rather big, only took 4 sec. 

I can make some exact stats if you'd like.

//Spider

Stephen Lavedas wrote:
> 
> I find that parsing really large text files takes MUCH longer than
> running the while loops in POVRay (or the math).  TRUE, the external
> code may GENERATE the files faster, but unless you move the macros into
> POVRay internally (patch them in) I don't think you will increase speed
> of parsing.  Perhaps some not too large group of objects may parse
> faster than they can calculate and parse, but when files approach 500k
> to a meg, then parse MUCH slower than the calculations take.  This is
> only from my experience, but I've just finished my Connected Sphere
> macro, and comparing it to the same input from a file (granted some
> redundant input) it takes FAR less time even though it is calculating at
> the time.
> 
> Steve
> 
> Spider wrote:
> >
> > Whoa..
> > I'm just wondering a bit here...
> > Is there an interest/objection in me porting some more of the larger #macros for
object to
> > an external program??? of course, credits will be given..
> >
> > As for why I am wondering, is from my interest... since I run a p-166 it's pretty
slow in
> > parsing, and once I have made a final object with settings I like, I'd like to
speed it
> > up... This is as far as I know one of the better ways. (I know, #debug,
#fwrite....)
> > Any ideas/demands/objections will be welcome. As for now, I do what I want, and
> > brutally...(hard coded)
> >
> > As for programming level, it'd probably be in win32 mode, since it is easier to
write once
> > I've made the algorithms... And it is easier to develop some more...
> >
> > well, respond....
> >
> > //Spider

Post a reply to this message