-
Notifications
You must be signed in to change notification settings - Fork 38
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
Comments
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
In theory these files could be cached, to speed up updating:
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.
The text was updated successfully, but these errors were encountered: