Hi! :waving_hand: Today, I ran some benchmarks to compare real-life launch times for first-time users of Julia 1.9.0-beta3 vs Julia 1.8.5. That means people who just installed Julia on their computer, and they are excited to get started! Results Summary of three samples, details below. I found tha…

I also agree this thread seems a bit surprising. For first time users, we could print a special message, “Hold tight while we precompile your packages to make everything go fast!” and then what you’re calling a loss turns into a win, because if they know why it’s happening most users will be patient…

One workflow that might be nice interactively is something like ] activate --copy which creates a new environment that copies the current Project.toml and Manifest.toml over. That way you don’t have to pay a precompilation price when doing one-off things, but your state is saved if you want to retur…

If I’m doing exploratory analysis, I do use my usual tools in a shared environment. Once there’s something that works I may snapshot that and save it in a project.

How do you snapshot an environment?

Could Pkg.add perhaps add the latest compatible locally installed version? I want add to add things a.s.a.p., and update can take time to update. I use separate environments for different scripts, and often use packages with large dependency trees like ModelingToolkit and Makie. When adding these p…

I guess I just don’t get why you want to use separate environments for everything if you still want to use all the versions you got from the outer environment. To me this sounds like a request to make Pkg.add worse to support a workflow that doesn’t really make sense (to me at least).

[image] Workflow for forking an environment General Usage I have a “main” environment that has a lot of the packages I use. Whenever I want to try something out, I go to a new directory and I want to use those packages plus a couple of other packages. I don’t want to rei…

I don’t make separate environments for everything, but say if it is a separate project for work, I do. I don’t know if a Pkg.add that prefers adding already locally available packages is worse. It is faster, and separates updating and adding more clearly. Of course if a package is not available loc…

[image] lmiq: Pkg.UPDATED_REGISTRY_THIS_SESSION[] = true That, in your startup.jl file, does that. I has been discussed if that should be the default.

Copy the environment files and then delete things I’m not using in the new copy. At that point I would probably also try updating everything in that environment and make sure it still works.

Isn’t the exact reproducibility of the environment overrated? I mean, having it is a nice feature. But don’t we actually expect that updating all non breaking versions still keeps everything working? Maybe there should be another level of “instantiation”, that adds the latest available non breakin…

First Pluto notebook launches are slower on Julia 1.9 beta 3

Internals & Design

jar1 January 27, 2023, 10:36pm 93

Topic		Replies	Views
Julia 1.9.0-beta2 precompilation taking almost twice as long General Usage question , precompilation	38	3462	January 30, 2023
New Julia versions, higher Pluto loading times General Usage ttfx	38	2001	February 4, 2026
10-15 minute TTFP with Plots.jl... Please help New to Julia ttfp	55	3220	January 9, 2023
Everything precompiling when opening new notebook Performance question	8	1059	July 21, 2022
Precompilation takes ages General Usage	14	1895	January 5, 2024

First Pluto notebook launches are slower on Julia 1.9 beta 3

Related topics