Am 23.05.2018 um 16:38 schrieb Stephen:
> On 23/05/2018 13:55, clipka wrote:
>> Am 23.05.2018 um 10:22 schrieb Stephen:
>>
>>> Test:
>>>
>>> v 3.8.0-alpha.9475849+av541.msvc14 is faster than
>>> v 3.8.0-x. tokenizer.9999+av5 60.msvc
>>>
>>> On the second run of the file. The parse time was a second or two slower
>>> than the first time. Except when using Ver 3.7 when it was the same.
>>
>> I take that as good news, presuming the scene in question does call
>> macros across files. Such a scenario would explain the superior
>> performance of v3.8.0-alpha over v3.7.0 as the result of macro caching,
>> as well as the inferior performance of v3.8.0-x.tokenizer vs.
>> v3.8.0-alpha as the result of disabled macro caching.
>>
> 
> Sorry it does not use macros. It did but I de-constructed the grass
> macro it was using as it was declaring an array of meshes from within a
> while loop. [Watch the memory usage rise and the HDD thrash.]

Hmm... then that begs the question, which change between v3.7.0 and
v3.8.0-alpha would have improved parsing speed?

Besides, what loop size are we talking about? Would that happen to be
>64k characters in the loop body?

> I have already had jr complain that I sent him the code in one file and
> not split into include files.
> So, what is wrong with 54317 lines in one file, anyway? ;-)

Nothing. It might actually be perfect for my parser tests. ;)

Post a reply to this message