Re: Test reader speed of Guile 3.0.6

[Dr. Arne Babenhauserheide]

David Kastrup <dak@gnu.org> writes:
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>> Han-Wen Nienhuys <hanwenn@gmail.com> writes:
>>> On Wed, Mar 10, 2021 at 8:23 AM Dr. Arne Babenhauserheide
>>> <arne_bab@web.de> wrote:
>>>> there’s a Guile 3.0.6 release planned that includes a rewrite of the
>>>> reader in Scheme. It has speed in the same order of magnitude as the
>>>> previous reader but might have different performance characteristics.
>>>>
>>>> If I remember correctly, lilypond uses the reader a lot, so if you have
>>>> a test-system with lilypond on Guile 3, could you test how running
>>>> lilypond with the current Guile master from git affects lilypond?
>>>
>>> last time I looked, building GUILE 3 from source was truly glacial,
>>> making this kind of thing annoying to check.
>>
>> If you build from tarball it is much faster, because it then provides
>> pre-created bootstrapping files. What’s so slow is creating the initial
>> optimized reader.
>>
>>> You say "same order of magnitude". Do you have benchmarks so we know
>>> what to expect?
>>
>> The current *average* spead of the reader is roughly 80% of the reader
>> implemented in C, but with different performance characteristics. I’m
>> asking here because I want to avoid surprising and avoidable changes
>> that block Lilypond. I consider Lilypond to be the most important
>> flagship project of Guile, and I want to do what I can to prevent
>> unnecessary friction.
>
> Sadly, you are not likely to block LilyPond.  The compilation
> instructions for LilyPond strongly recommend using version 1.8.8 (or the
> branch tip catered for by Thien-Thi Nguyen) since all other versions are
> vastly slower and less stable.

I know. That’s something for which I hope that it will change.

And I really don’t want to work backwards on that path.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken

signature.asc
Description: PGP signature