[Fontconfig-bugs] [Bug 64766] Make fontconfig scanning faster

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64766

Behdad Esfahbod <freedesktop at behdad.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |freedesktop at behdad.org

--- Comment #2 from Behdad Esfahbod <freedesktop at behdad.org> ---
(In reply to comment #1)
> (In reply to comment #0)
> > Looking at profiler output, most time when scanning a font is spent inside
> > of freetype below FT_Load_Glyph. (Something about running the truetype
> > bytecode interpreter...) Is that really needed for basic fontconfig
> > functionality?
> 
> That is required to let fontconfig know what the glyph coverage a font has.

We should force hinting off though.

> > The 2nd case is worse: changing a single file in a directory containing
> > fonts forces the whole directory to be scanned. Can't caching be done on a
> > per-file basis?
> 
> I don't see what you really mean. in fact fontconfig do cache a font per
> file.

When a directory changes, we rescan the entire directory to rebuild the cache
for that dir.

> > For some users this is a deal breaker, and they're asking for hacks to
> > remove fontconfig usage etc. It would be nice if fontconfig could solve this
> > issue by optimizing the scan process and making the caching more clever.
> 
> I don't know how often it happens though, they may see something like
> annoyance in fontconfig without creating a cache before doing something on
> their fontconfig-based applications. this is why fontconfig is going to
> create a cache though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20130520/b07b6c02/attachment.html>