Re:Julia 1.6: what has changed since Julia 1.0?
by cbkeller on Sunday February 14, 2021 @12:35PM
(#26134257)
It’s not trivial to do, but compiling plots into your sysimg might actually fix that
[ Parent
| on HN ]
Re:Julia 1.6: what has changed since Julia 1.0?
by enriquto on Sunday February 14, 2021 @12:36PM
(#26134268)
Thanks! Is there a way to compile all installed packages into the sysimage? If so, why isn't that the default?
Re:Julia 1.6: what has changed since Julia 1.0?
by cbkeller on Sunday February 14, 2021 @12:45PM
(#26134350)
Technically yes, but then IIRC you’d have to recompile the whole sysimg any time you update any single package, which could get to be a pain. The usual compromise seems to be to include just a handful of your most used packages in the sysimg (say Plots + Revise)
Re:Julia 1.6: what has changed since Julia 1.0?
by enriquto on Sunday February 14, 2021 @12:55PM
(#26134444)
> you’d have to recompile the whole sysimg any time you update any single package
Are there any downsides to this? You never care how long does a system update take. You always care how long do your programs run.
Re:Julia 1.6: what has changed since Julia 1.0?
by Sukera on Sunday February 14, 2021 @02:21PM
(#26135305)
The downside is that PackageCompiler (or SnoopCompile, for that matter) can only pack into the sysimage what it sees. This is usually done by "recording" which methods get called during a session and putting the compiled native code for those into the sysimage. If it's not called during setup, you'll still have dynamic compilation (as for any code that hasn't ever run).