-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Precompilation does not produce a deterministic result #25900
Comments
@vtjnash, any idea what's up here? |
This is the same as #24383 but for master and not 0.6.1/2, no? |
Possibly, but I don't think that issue showed that the result of precompilation fluctuates wildly from run-to-run even when nothing changes in terms of the code itself (neither the code being compiled nor the julia version). #24383 might be a bug, or it might mean that we're using the wrong strategy; this issue clearly indicates a bug. Of course they might have the same root cause. |
#24383 is also JuliaIO/FileIO.jl#156 where fluctuations are shown. I see the same fluctuations on 0.6.2 |
Any way the non-determinism will be fixed? I tried precompiling in a (theoretically) clean environment versioninfo()
Julia Version 1.0.0
Commit 5d4eaca0c9 (2018-08-08 20:58 UTC)
Platform Info:
OS: Linux (x86_64-unknown-linux-gnu)
CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.0 (ORCJIT, skylake) ``` |
Is anybody looking at this? I find non-determinism scary |
Progresses #34753 here! |
This is essentially a copy of JuliaPlots/Plots.jl#1379. I tested the precompilation of FileIO, commit fd7bf2f800d9119f2720a9054f7a319549eb2c8d with a
using Nullables
thrown in to make it build onHere are the results of multiple rounds of precompilation (I used
using Example
to make sure the code-loading machinery itself had been compiled):You can see that both the startup time and file sizes varied by more than a factor of 2, without any change to FileIO's code. Slower startup seems to be associated with bigger files.
The text was updated successfully, but these errors were encountered: