I've been working on a project using lyluatex, which, while producing superior output compared to lilypond-book, has significantly slower compilation speeds. Over the past few weeks, I've noticed that compiling multiple .lytex files in the same directory leads to a cluttered cache folder (tmp-ly). This seems to slow down occasional recompilations, presumably because lyluatex has to search through a large number of files in the cache.
Hypothesis for Slowdown: I assume that the slowdown occurs because lyluatex needs to check for existing files in an already large cache folder, which negates the speed benefits of having a cache.
Suggested Solutions:
- Generate a cache with a unique name based on the
.lytex file name.
- Organize cache files into subdirectories within
tmp-ly to ensure each .lytex file has its own cache space.
- Implement dual modes of operation: one for projects with shared LilyPond files and another for single projects with multiple files in the same folder.
Currently, the cache mechanism seems beneficial for projects referencing the same LilyPond files across different projects but is inefficient for a single project divided into multiple files (each of those referencing different LilyPond files) in one folder.
I've been working on a project using
lyluatex, which, while producing superior output compared tolilypond-book, has significantly slower compilation speeds. Over the past few weeks, I've noticed that compiling multiple.lytexfiles in the same directory leads to a cluttered cache folder (tmp-ly). This seems to slow down occasional recompilations, presumably becauselyluatexhas to search through a large number of files in the cache.Hypothesis for Slowdown: I assume that the slowdown occurs because
lyluatexneeds to check for existing files in an already large cache folder, which negates the speed benefits of having a cache.Suggested Solutions:
.lytexfile name.tmp-lyto ensure each.lytexfile has its own cache space.Currently, the cache mechanism seems beneficial for projects referencing the same LilyPond files across different projects but is inefficient for a single project divided into multiple files (each of those referencing different LilyPond files) in one folder.