Use a local compilecache, sync after execution. #108
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Sounds good to me. I had some code that does much the same for mirroring srccache downloads |
Member
Author
|
Is it something you would recommend PkgEval doing (given how our code loading/precompilation works)? Because it seems that another run without this is working fine, so the slowdown I noticed may have been caused by another bug. |
Member
|
Yep, that is how our precompilation is supposed to be designed to work for |
Member
Author
|
Lots of tests failed with e.g.: See https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_date/2022-08/03/report.html So I think we'll need this... |
32 tasks
maleadt
force-pushed
the
tb/compilecache
branch
from
585aedd to
83bc61c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed some slowdown after adding a shared compilecache to Nanosoldier, and I'm thinking this may be due to workers running into one another while precompiling packages. So let's try this out: packages are precompiled into a local compilecache (
~/.julia/.../compiled), and after completion copied into a global cache that's mounted read-only at the system depot (/usr/local/share/julia).@vtjnash Any thoughts? The reason I want to share the compile cache, is that when running under
--bug-reportwe otherwise precompile BugReporting.jl's dependencies over and over again. This makes e.g. Example.jl take 30 sec to install/test, whereas it normally only takes 3. Sharing the compilecache gets it down to ~10 sec.