Do not use benchmark request index when inserting release artifacts#2401
Merged
Kobzol merged 3 commits intorust-lang:masterfrom Feb 11, 2026
Merged
Do not use benchmark request index when inserting release artifacts#2401Kobzol merged 3 commits intorust-lang:masterfrom
Kobzol merged 3 commits intorust-lang:masterfrom
Conversation
We'll try to do 20 `INSERT` queries every 30 seconds, which doesn't sound so terrible.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is an experiment to see how expensive it would be to just try to insert all the release artifacts everytime the job queue runs.
I think that it will be fine (I'll check in logs), but if not, we can do it less frequently - surely we don't need to check released artifacts, which appear maybe once a week on average, every thirty seconds :)
It takes ~200ms locally to run this, but on production the DB latencies will be higher.
If the experiment is successful, I will do the same for the master benchmark requests and then finally get rid of the benchmark index.