8
edits
Julia: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Marked this version for translation) |
No edit summary |
||
| Line 36: | Line 36: | ||
<!--T:8--> | <!--T:8--> | ||
In the example above, installing just the JLD package creates a <code>~/.julia</code> tree with 18673 files and directories and using 236M of space, almost 5% of a standard user's quota for <code>/home</code>. It's worth remembering that installing a lot of packages will consume a lot of space. | In the example above, installing just the JLD package creates a <code>~/.julia</code> tree with 18673 files and directories and using 236M of space, almost 5% of a standard user's quota for <code>/home</code>. It's worth remembering that installing a lot of packages will consume a lot of space. | ||
If you often need to update your Julia installation, or have a large/complex installation (and environments), you can redirect Julia's package manager to a different location, by: | |||
$ mkdir -p <yournewdirectory> | |||
$ export JULIA_DEPOT_PATH=<yournewdirectory> | |||
$ mv ~/.julia ~/juliabak # preserve existing, but remove it to avoid clashes | |||
$ module load julia | |||
Any subsequent package operation will now write to the directory you specified. | |||
Because Julia precompiles packages (>1.6), a distributed Julia program can cause a spike of read/writes to ~/.julia/compiled. By configuring Julia to use (faster) storage you can avoid unnecessary slowdowns. [https://docs.julialang.org/en/v1/base/constants/#Base.DEPOT_PATH Configuring DEPOT_PATH.] | |||
Preserving a julia installation can be done by compressing the contents of DEPOT_PATH. For example, if you decompress on fast local storage, but want to preserve on ~/project (compressed). However, note that the paths are hardcoded, so decompression should be done in an identically named path. | |||
= Available versions = <!--T:9--> | = Available versions = <!--T:9--> | ||