## Summary
We use this profile in uv to create success, as an optimization for the
iterative test loop. We include `opt-level=1` because it ends up being
"worth it" for testing (empirically), even though it means the build is
actually a big slower than `dev` (if you remove `opt-level=1`, clean
compile is about 22% faster than `dev`).
Here are some benchmarks I generated with Claude -- the main motivator
here is the incremental testing for `ty_python_semantic` which is 2.4x
faster:
### `ty_python_semantic`
Full test suite (471 tests):
| Scenario | dev | fast-test | Improvement |
|-------------|-------|------------|-------------|
| Clean | 53s | 49s | 8% faster |
| Incremental | 17.8s | 6.8s | 2.4x faster |
Single test:
| Scenario | dev | fast-test | Improvement |
|-------------|-------|------------|-------------|
| Clean | 42.5s | 55.3s | 30% slower |
| Incremental | 6.5s | 6.1s | ~same |
### `ruff_linter`
Full test suite (2622 tests):
| Scenario | dev | fast-test | Improvement |
|-------------|-------|------------|-------------|
| Clean | 31s | 41s | 32% slower |
| Incremental | 11.9s | 10.5s | 12% faster |
Single test:
| Scenario | dev | fast-test | Improvement |
|-------------|------|------------|-------------|
| Clean | 26s | 36.5s | 40% slower |
| Incremental | 4.5s | 5.5s | 22% slower |