Everything precompiling when opening new notebook

[mkitti]

@Andy2K11

If I’ve understood correctly, an update to one package will cause a recompilation to all its dependencies, so maybe there is some good practice of running updates and precompiling your environment again; when you’re off to get a coffee and not when you’re in the middle of a task?

It could, yes. In development, Revise.jl can mitigate this effect. It’s best to keep environments minimalist. Also note that environments stack:

https://docs.julialang.org/en/v1/manual/code-loading/#Environments-1

GitHub - timholy/Revise.jl: Automatically update function definitions in a...

@Andy2K11

There is a performance tips page in the manual, though that didn’t seem relevant to this kind of problem, is there any general guide for workflows in Julia or is it simple enough to say that when you’ve launched a repl you should keep it open - all my programs and notebooks are a lot faster after the first run?

I usually use the Revise-based workflow described below.

https://docs.julialang.org/en/v1/manual/workflow-tips/#Revise-based-workflows

@Erik_Engheim nicely illustrates this here:

Workflow for Developing Code in a Julia REPL