Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache package databases #335

Open
lazka opened this issue Oct 31, 2023 · 1 comment
Open

Cache package databases #335

lazka opened this issue Oct 31, 2023 · 1 comment

Comments

@lazka
Copy link
Member

lazka commented Oct 31, 2023

In theory these files could be cached, to speed up updating:

$ ls /var/lib/pacman/sync/
clang32.db         clang64.files         mingw32.db         mingw64.files      staging.db
clang32.db.sig     clang64.files.sig     mingw32.db.sig     mingw64.files.sig  staging.files
clang32.files      clangarm64.db         mingw32.files      msys.db            ucrt64.db
clang32.files.sig  clangarm64.db.sig     mingw32.files.sig  msys.db.sig        ucrt64.db.sig
clang64.db         clangarm64.files      mingw64.db         msys.files         ucrt64.files
clang64.db.sig     clangarm64.files.sig  mingw64.db.sig     msys.files.sig     ucrt64.files.sig

It will still hit the repo and mirror but should result in a 304 in most cases, assuming the mtime gets restored correctly.

Question is if we should cache them separately. Probably better, assuming we restore in parallel, since they might change more often than packages and invalidate the caches needlessly otherwise.

@lazka
Copy link
Member Author

lazka commented Mar 11, 2024

Since msys2/msys2-main-server@a70664c we no longer hit the mirrors when checking an up-to-date DB, which shaves of another 400ms if we implement this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant