The amount that can be precompiled has greatly increased in 1.8 compared to 1.7, see e.g. Improvements in package precompilation | Tim Holy & Valentin Churavy | JuliaCon 2022 - YouTube . Because Pluto runs each notebook in its own environment, you more or less pay that precompilation cost each time you start the notebook. (There is some fine print about the precompilation cache here.) The short example here that has a lot of “big” packages highlights this. However, if you look at the first call to do meaningful work after the setup cell, it will probably be faster on 1.8, which does matter a lot for reactive notebooks.
1 Like