I'm glad to see that they are making improvement to latency issues. It has always been an issue for me the fact that you need to way several seconds for basic packages to load. I don't think you need to pre-jit so much code to make this work.

People are being downvoted to oblivion for mentioning this, but for some of us coming from different languages, it definitely takes some time to get used to things. I'm new to julia, so am probably more ignorant about this than most... but importing two packages such as DifferentialEquations and Plots, on my very modern machine takes ~30seconds (this is after they've been "precompiled"). I'm curious, assuming I haven't installed anything new, or haven't changed my installation, why does julia not cache this complied binary somewhere? It seems like this long step has to happen on each new-kernel import, but perhaps it could be avoided? Having an option flag that would cause julia to redo the compilation (because the user has, say, changed something about their installtion), seems like a simple solution.

What am I missing?

There will be more caching in the future, but until then it sounds like you'd like PackageCompiler.jl (https://github.com/JuliaLang/PackageCompiler.jl) to build DiffEq and Plots into your sysimage.