Re: Speedup with recent lilypond

Thanks! Am 24.04.2017 um 09:39 schrieb Phil Holmes: - Original Message - From: "Michael Käppler" <xmichae...@web.de> To: "David Kastrup" <d...@gnu.org> Cc: <lilypond-user@gnu.org> Sent: Monday, April 24, 2017 8:24 AM Subject: Re: Speedup with recen

Re: Speedup with recent lilypond

- Original Message - From: "Michael Käppler" <xmichae...@web.de> To: "David Kastrup" <d...@gnu.org> Cc: <lilypond-user@gnu.org> Sent: Monday, April 24, 2017 8:24 AM Subject: Re: Speedup with recent lilypond I'm on Win7 x64. When has the fon

Re: Speedup with recent lilypond

Michael Käppler writes: > I'm on Win7 x64. When has the font caching been fixed? I could not > find the commit. If I remember correctly, this was an update in GUB, our crosscompiling setup. Probably preceded by some upstream change of whatever library was involved. --

Re: Speedup with recent lilypond

I'm on Win7 x64. When has the font caching been fixed? I could not find the commit. Am 24.04.2017 um 09:14 schrieb David Kastrup: Michael Käppler writes: Hi all, just for curiosity: I upgraded from 2.19.55 to 2.19.59 and noticed an enormous speedup. That is really great

Re: Speedup with recent lilypond

> [...] but an "enormous speedup" would likely be a fix of the > defective Freetype font caching. Just to be clear: FreeType itself provides font caching within the library. However, lilypond doesn't use this functionality (and right so). You rather mean problems with the fontconfig library.

Re: Speedup with recent lilypond

Michael Käppler writes: > Hi all, > > just for curiosity: I upgraded from 2.19.55 to 2.19.59 and noticed an > enormous speedup. That is really great > > and I would like to know which change(s) are responsible for that. You did not mention your operating system, but an