-
Notifications
You must be signed in to change notification settings - Fork 37
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
Huge precompilation overhead #553
Comments
Hey @ChenZhao44 could you tell me what OS is on this cluster? I'd like to recreate your environment if possible and do some profiling. I'm aware it takes some time on initial precompilation but never run into a case like this. |
Thanks @johnzl-777 . Here is the OS information
|
@ChenZhao44 could I get the version of Julia you're using as well? Much appreciated! |
julia> versioninfo()
Julia Version 1.8.5
Commit 17cfb8e65ea (2023-01-08 06:45 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: 16 × Intel(R) Xeon(R) Gold 6134 CPU @ 3.20GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-13.0.1 (ORCJIT, skylake-avx512)
Threads: 1 on 16 virtual cores |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using Bloqade on a cluster. Previously, I used the separate library in Bloqade as a dependency, which included BloqadeExpr, BloqadeODE, BloqadeMIS, etc. It worked well, although the first time precompilation on a cluster took about 20 minutes.
However, I switched to using the full Bloqade as a dependency this week. The precompilation process has been ongoing for over 3 hours, but it is not providing any information on its progress as it is essentially a black box.
The text was updated successfully, but these errors were encountered: