-
Notifications
You must be signed in to change notification settings - Fork 5
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
select_executor
is slow
#76
Comments
As an extra datapoint: % julia --compile=min --project=/tmp --startup-file=no -q
julia> using Sandbox; @time @eval Sandbox.select_executor(false)
0.366757 seconds (838.45 k allocations: 42.643 MiB, 3.60% gc time, 81.86% compilation time)
UnprivilegedUserNamespacesExecutor |
I believe most of the time is spent compiling https://github.com/staticfloat/Sandbox.jl/blob/ed87f079edb1cef60c32ad5fbfbcd38c70a1314a/src/Docker.jl#L31-L33 |
For the record, with JuliaLang/julia#47184 and % ./julia --startup-file=no -q --project=/tmp
julia> @timed @eval using Sandbox
(value = nothing, time = 0.180352858, bytes = -8781611, gctime = 0.0, gcstats = Base.GC_Diff(-8781611, 7, 0, 378317, 327, 0, 0, 0, 0))
julia> @time @eval Sandbox.select_executor(false)
0.006543 seconds (8.59 k allocations: 539.896 KiB)
PrivilegedUserNamespacesExecutor 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For comparison:
Note that by forcing the
Sandbox.jl
runner withthe time is cut from 4 to 3 seconds, still 300x slower than
BinaryBuilderBase.preferred_runner
. They're both type-unstable (of course), butSandbox.select_executor
seems to be particularly bad, even when forcing the runner.The text was updated successfully, but these errors were encountered: