POV-Ray : Newsgroups : povray.beta-test : Restructured Parser wants Testing : Re: Restructured Parser wants Testing Server Time
5 May 2024 19:16:53 EDT (-0400)
  Re: Restructured Parser wants Testing  
From: Stephen
Date: 24 May 2018 05:25:52
Message: <5b068520$1@news.povray.org>
On 23/05/2018 22:07, clipka wrote:
> Am 23.05.2018 um 21:55 schrieb Stephen:
> 
>>> Please go ahead. I'm curious which feature of the file makes
>>> v3.8.0-alpha like it better than v3.7.0.
>>>
>>
>> Done.
>> Posted in povray.binaries.scene-files as "Flowers for clipka"
>>
> 
> I think I nailed it: On my system I get just shy of 300 seconds parsing
> time on v3.7.0, a bit over 200 seconds on v3.8.0-alpha, and a bit shy of
> 200 seconds on v3.8.0-x.tokenizer.9673626 now.
> 
> Didn't bother to test with v3.8.0-x.tokenizer.9999, as I would have had
> to "rewind" to old source code, but I'm satisfied with having a
> reasonably plausible theory as to why it may have been slower.
> 

I ran the latest update to the tokenizer and here is a summary of the 
parse times.
Ver 3.7.0
   Parse Time:       0 hours  5 minutes 11 seconds (311.541 seconds)
Ver 3.8
   Parse Time:       0 hours  3 minutes 50 seconds (230.366 seconds)
Ver x.tokenizer.9999
   Parse Time:       0 hours  4 minutes 18 seconds (258.998 seconds)
Ver x.tokenizer.9673626
   Parse Time:       0 hours  3 minutes 19 seconds (199.541 seconds)


Aside.
I run Throttle.exe to monitor my CPU and GPU temperatures. I noticed 
that during the rendering of the scene. My CPU was being throttled back 
when I was using Ver 3.8 and the tokenizers. I cleaned my fans and 
filters last week so I don’t think it is an airflow problem.
Has anyone else noticed an increase in temperature with 3.8?


-- 

Regards
     Stephen


Post a reply to this message

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