POV-Ray : Newsgroups : povray.unofficial.patches : An updated povr tarball for Unix/Linux. b0bcf6c0 Server Time
7 Jul 2022 00:49:02 EDT (-0400)
  An updated povr tarball for Unix/Linux. b0bcf6c0 (Message 11 to 12 of 12)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: Mr
Subject: Re: An updated povr tarball for Unix/Linux. b0bcf6c0
Date: 13 May 2021 11:45:00
Message: <web.609d491dc0bd773c16086ed03f378f2@news.povray.org>
William F Pokorny <ano### [at] anonymousorg> wrote:
> On 4/26/21 7:42 AM, William F Pokorny wrote:
> > Ref:
> >
> >
http://news.povray.org/povray.binaries.programming/message/%3C6086a32c%40news.povray.org%3E/#%3C6086a32c%40news.pov
ray.org%3E
> >
> >
> > Web message: 6086a32c@news.povray.org
> >
> > ---
>
> In working with Tor Olav's idea for a more accurate VAngle macro, I
> discovered the lower case identifier checking(1) is far too expensive
> when making a million calls to a macro with internal #local identifiers.
>
> For now, I recommend configuration with --disable-no-lc-identifiers, if
> running scenes calling macros with internal identifiers a great many times.
>
> Bill P.
>
> (1) - I'm using c++11 regex at the moment. I've noted some complaints
> about performance of std regex, but whether it's that or just how our
> macros work in being re-read / interpreted on each call - I don't know.
> Might be significant expense is unavoidable and the case checking should
> not be the default behavior.

You seem to solve so many issues in that linux only branch, is there a chance
that some of those fix propagate to master or do they already? Sorry if this is
not what you were referring to at all, but  some unjustified overhead to the use
of separated pov macro files was mentioned numerous times by Clipka and
supposedly solved in his branch, just in case.


Post a reply to this message

From: William F Pokorny
Subject: Re: An updated povr tarball for Unix/Linux. b0bcf6c0
Date: 13 May 2021 16:20:30
Message: <609d8a0e@news.povray.org>
On 5/13/21 11:43 AM, Mr wrote:
> William F Pokorny <ano### [at] anonymousorg> wrote:
...
> 
> You seem to solve so many issues in that linux only branch, is there a chance
> that some of those fix propagate to master or do they already? 

They don't get into v3.8 master today as it is not being updated for a 
couple years. Where I believe fixes could be adopted more or less 
directly by the v3.8 master branch, I make a point to publish them on 
this news server or sometimes on github.

If mainstream work resumes, I have some hope the investigative 
information on issues will be of help, if not always my code changes.

> Sorry if this is
> not what you were referring to at all, but some unjustified overhead to the use
> of separated pov macro files was mentioned numerous times by Clipka and
> supposedly solved in his branch, just in case.
> 

I believe the v3.8 master branch, as it sits, has all Christoph's 
completed macro performance enhancements. So my branch, hgpovray38 and 
qtpovray have them too being based on that code - unless I've missed 
something.

Bill P.


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2021 Persistence of Vision Raytracer Pty. Ltd.