[Fontconfig] Application startup performance

Raimund Steger rs at mytum.de
Sun Jan 17 14:19:02 PST 2016


On Sun, 17 Jan 2016 21:56:53 +0100
Raimund Steger <rs at mytum.de> wrote:

> On Thu, 14 Jan 2016 22:39:37 -0800
> Keith Packard <keithp at keithp.com> wrote:
> 
> > Akira TAGOH <akira at tagoh.org> writes:
> > 
> > > As I mentioned in other mail, it was needed to avoid the races. to get
> > > rid of it completely, the logic of the cache updates may needs to be
> > > changed because keeping the directory information into the memory a
> > > long time causes that issue easily when recursively traversing
> > > directories.
> > 
> > As long as the timestamp written to the cache is the directory change
> > time when the scanning starts, then applications starting after that
> > will re-scan the directory if it was changed while the first application
> > was scanning. I guess I don't see how this (which is what I think the
> > code does) could cause a race?
> 
> Wouldn't it need to be the timestamp that was used in the very first call to FcCacheTimeValid? But it's not implemented like that, is it?

Ah scratch that, seems to be OK after all, there's a stat in FcDirCacheScan.




-- 
Worringer Str 31 Duesseldorf 40211 DE  home: <rs at mytum.de> 
+49-179-2981632 icq 16845346           work: <rs at interface-ag.de>


More information about the Fontconfig mailing list