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

Reduce scans of experiment_crates to find next crate #752

Merged
merged 1 commit into from
Dec 8, 2024

Conversation

Mark-Simulacrum
Copy link
Member

These scans are relatively expensive, so instead we internally cache a small amount of crates. The expectation is that this should allow us to scan ~once rather than repeatedly re-scanning as time goes by. I experimented with a partial index but didn't get any meaningful results (possibly made things worse), it's not super clear why, but the hope is that this is more or less just an improvement.

These scans are relatively expensive, so instead we internally cache a
small amount of crates. The expectation is that this should allow us to
scan ~once rather than repeatedly re-scanning as time goes by. I
experimented with a partial index but didn't get any meaningful results
(possibly made things worse), it's not super clear *why*, but the hope
is that this is more or less just an improvement.
@Mark-Simulacrum Mark-Simulacrum added this pull request to the merge queue Dec 8, 2024
Merged via the queue into rust-lang:master with commit 6ba3a90 Dec 8, 2024
3 checks passed
@Mark-Simulacrum Mark-Simulacrum deleted the debug-crater branch December 8, 2024 13:35
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

Successfully merging this pull request may close these issues.

1 participant