<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Make fontconfig scanning faster" href="https://bugs.freedesktop.org/show_bug.cgi?id=64766#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Make fontconfig scanning faster" href="https://bugs.freedesktop.org/show_bug.cgi?id=64766">bug 64766</a> from <a class="email" href="mailto:nfxjfg@gmail.com" title="nfxjfg@gmail.com">nfxjfg@gmail.com</a> <pre>> That is required to let fontconfig know what the glyph coverage a font has. Somehow freetype seems to spend rather a lot of effort on that. I don't know how this stuff works, but to my naive eyes is looks like there's further optimization possible, though possibly that would require changes in freetype instead of fontconfig. >> When a directory changes, we rescan the entire directory to rebuild the >> cache for that dir. > I have no idea how this can be improved though. For example, the granularity of the cache could be changed and create a new cache for every 20 files or so. Or it could be made such that the old cache is reused for files that have not changed. No doubt, these changes would be intrusive to the cache code, but given the problems with font scanning times, I think it would be worth it. Now that you have added a hash for each font, maybe it would be possible to cache the results for memory fonts as well? Hashing actually makes loading a font even slower, but since you're doing it anyway, maybe it could be used for that purpose as well.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>