A smaller performance hotspot (also confirmed via profiling) seems to be checking if jars exist on disk. We could introduce a per-run cache for this information, which we would however have to invalidate when we know this information changes. A file system cache could also help speed up task specific caching checking last modified times of source files and class files, etc.
A smaller performance hotspot (also confirmed via profiling) seems to be checking if jars exist on disk. We could introduce a per-run cache for this information, which we would however have to invalidate when we know this information changes. A file system cache could also help speed up task specific caching checking last modified times of source files and class files, etc.