GenieFramework / GenieFramework/GenieDeployDocker.jl
JULIA_DEPOT_PATH setting after precompilation reduces container startup performance
- Dominant language
- Julia
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
In the Dockerfile created by this plugin, the following setup reduces performance: Initially, packages are precompiled with
```
RUN julia -e "using Pkg; Pkg.activate(\\".\\"); Pkg.instantiate(); Pkg.precompile(); "
```
_After_ this statement, the Julia depot path is changed with
```
ENV JULIA_DEPOT_PATH "/home/$user/.julia"
```
When starting a container, Julia will look for cached compiled package images in the new depot path and will not find any (as they reside in the default location used for the first statement, before setting the env variable). This will trigger a unnecessary recompilation.
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the generated Dockerfile and the order of the Julia precompilation command and JULIA_DEPOT_PATH setting. Ensure the depot path used during precompilation matches the path used when the container starts, then verify that startup does not trigger unnecessary recompilation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, julia
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100