Re: scratch/igc: Implications of MPS being asynchronous

[Gerd Möllmann]

Pip Cet <pipcet@protonmail.com> writes:

>> Something like that, yes. Or maybe just clear the font caches completely
>> when some criterion is met? Time, size, something else, no idea.
>
> That's what I meant: we use a dummy sentinel to detect a GC cycle, then
> we trigger font cache compaction and re-enable GC cycle detection
> afterwards.  We might want to add an additional delay or a flag se we
> don't actually do anything in compact_font_caches if we know there
> hasn't been a change.

I think I understood what you mean. What I meant is something completely
independent of GC. For example:

- Run a function every N seconds which completely clears a font cache when
  it has more than M entries. Or deletes all entries not having been
  used for O seconds, or whatever.

- Or on cache use: When looking up a cache entry, when say there are >N
  entries, delete the entries that haven't been used for the longest
  time.

Or other criteria like that, but without involving GC.

Or do something involving GC, of course :-).