# How uv Achieved Its Performance

Andrew Nesbitt's ["How uv got so fast"](https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html) explains that [uv](https://pydevtools.com/handbook/reference/uv.md)'s speed comes less from Rust and more from eliminating work entirely.

## Speed Through Elimination

Rather than optimizing slow code paths, [uv](https://pydevtools.com/handbook/reference/uv.md) just removes them:

* No `.egg` support
* No `pip.conf`
* No bytecode compilation by default
* Ignoring `requires-python` upper bounds reduces resolver backtracking

## Rust-Independent Optimizations

Many of [uv](https://pydevtools.com/handbook/reference/uv.md)'s performance gains could work in [pip](https://pydevtools.com/handbook/reference/pip.md):

* Parallel downloads instead of sequential
* Smart HTTP range requests for metadata

[uv](https://pydevtools.com/handbook/reference/uv.md) got fast by launching when PEP 658 infrastructure was ready and by skipping backward compatibility requirements that slow down [pip](https://pydevtools.com/handbook/reference/pip.md).

Read the [full article](https://nesbitt.io/2025/12/26/how-uv-got-so-fast.html) for the complete analysis.