Improve performance of generic repo #155
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The APT and RPM repos work on a locally-synced copy of their S3 prefixes
(because the repo tooling expects repos to be in a local fs), but the
generic repo currently just reads/writes things to S3 directly. This is
problematic for atomicity and performance reasons.
Fix this by doing the S3 sync for the generic repo as well. While at
it, lower log levels on some things to reduce noise.
This was tested locally (running
process_incoming.py
on artifactsproduced with local
gel-pkg
runs).