<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Make fontconfig scanning faster"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64766">64766</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>fontconfig-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>Make fontconfig scanning faster
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>freedesktop@behdad.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>nfxjfg@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>library
</td>
</tr>
<tr>
<th>Product</th>
<td>fontconfig
</td>
</tr></table>
<p>
<div>
<pre>Scanning new fonts is pretty slow. There are two cases where this is quite
noticeable: 1. adding big fonts from memory, and 2. adding/removing fonts to
directories with many fonts. The 2nd case happens typically only on OSX,
obscure Linux systems, or MS Windows, but the 1st is a problem on all
platforms.
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?
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?
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>