[Fontconfig] Application startup performance

[Behdad Esfahbod]

Any resolution here?  Current master's behavior of stating all fonts is
definitely very bad.  Anyone volunteer to clean up the cache code a bit?

On Mon, Jan 18, 2016 at 7:09 PM, Akira TAGOH <akira at tagoh.org> wrote:

> On Mon, Jan 18, 2016 at 5:54 PM, Keith Packard <keithp at keithp.com> wrote:
> > Akira TAGOH <akira at tagoh.org> writes:
> >
> >> Not exactly. fontconfig doesn't stat everey directory at runtime but
> >> relies on the subdir list in the cache to traverse. so if it isn't
> >> outdated and missing some, it won't be picked up by fontconfig.
> >
> > How can it "miss some" if it checks the timestamp of the parent before
> > relying on the list?
>
> Previously fontconfig only locks the file when writing out. the time
> to write it out since bringing up fc-cache depends on the time of
> collecting data and it takes more time if there are more targeted
> files and directories. and likely to see a process finished first
> which brought up later.
> so I locked out between reading and writing to avoid it.
>
> >> Not sure but perhaps it is. my memory is already vague and not sure if
> >> it had a nano second in the mtime. so better testing anyway.
> >
> > Hrm. Is fontconfig even using the higher resolution time when the file
> > system supports it?
>
> Yes. well, very recently. not yet included in any releases.
>
> --
> Akira TAGOH
> _______________________________________________
> Fontconfig mailing list
> Fontconfig at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/fontconfig
>



-- 
behdad
http://behdad.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig/attachments/20160310/92886e4c/attachment.html>