Skip to content

Reconsider using Pkg server by default for the registry #14

@KristofferC

Description

@KristofferC

In 1.7, Pkg has moved to use a compressed registry by default. This avoids unpacking ~22 000 files and has some good performance improvements for the first time installing a registry (which is what CI does all the time):

git :

julia> @time Pkg.add("Example")
  Installing known registries into `~/.julia`
     Cloning registry from "https://github.com/JuliaRegistries/General.git"
       Added registry `General` to `~/.julia/registries/General`
   Resolving package versions...
    Updating `/tmp/jl_nJuAcb/Project.toml`
  [7876af07] + Example v0.5.3
    Updating `/tmp/jl_nJuAcb/Manifest.toml`
  [7876af07] + Example v0.5.3
 15.838710 seconds (8.68 M allocations: 301.542 MiB, 0.29% gc time, 1.04% compilation time)

pkg server:

julia> @time Pkg.add("Example")
  Installing known registries into `~/.julia`
    Updating registry at `~/.julia/registries/General.toml`
   Resolving package versions...
    Updating `/tmp/jl_16gHZs/Project.toml`
  [7876af07] + Example v0.5.3
    Updating `/tmp/jl_16gHZs/Manifest.toml`
  [7876af07] + Example v0.5.3
  2.753616 seconds (5.57 M allocations: 355.760 MiB, 1.80% gc time, 0.09% compilation time)

This is on my Linux machine with a fast hard drive. On windows, the difference is much larger.

By the time #6 was merged, the Pkg server would only serve the updated General once all the packages and artifacts were available. This is no longer the case and the Pkg server serves the updated registry straight away.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions