Hi Yuriy, thanks for explaining. I’ve also experienced persistent idle CPU usage with a large font library, so this topic is relevant to me.
I understand that initial indexing and processing changes will require more resources with larger collections. Would you consider event-driven folder monitoring to reduce the work needed when nothing has changed?
On Windows, ReadDirectoryChangesW supports change notifications for a directory tree, and Node’s fs.watch uses that mechanism. An initial scan followed by targeted updates could potentially keep the library synchronized with much lower idle CPU usage.
I appreciate that notification overflows, junctions, disconnected drives, and network folders require careful handling. Occasional reconciliation scans or fallback polling might still be necessary.
Is this an approach the team would consider, or are there constraints in FontBase’s architecture that make it difficult? Keeping a large collection available and synchronized while minimizing background CPU use would be a valuable improvement, particularly for laptop battery life.
Thanks for considering it.