[ty] Enable optimizations for salsa in debug profile#18117
Merged
MichaReiser merged 1 commit intomainfrom May 15, 2025
Merged
Conversation
Contributor
|
Glyphack
pushed a commit
to Glyphack/ruff
that referenced
this pull request
May 21, 2025
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.
Summary
We use salsa a lot and it changes infrequently. This PR enables more aggressive optimizations for the salsa crate when using the debug profile.
This should give us faster test (and ty execution) at the cost of slightly longer compile times when compiling a new salsa version for the first time.
Test Plan
This reduces the wall time for
cargo nextest run -p ty_python_semantic --test mdtestfrom ~4s to ~3.3s on my machine