Benchmarks should disable package builds

Open Beginner friendly
#37 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
performance

Research direction

Start by locating the benchmark commands that install and resolve packages, then reproduce the reported slowdown involving python-rapidjson. Update the benchmark setup to use the proposed no-build or binary-only behavior, and verify that package build time is excluded and the benchmark no longer shows the reported regression.

Written by the indexing model from the issue text.

Description

We got a report over in https://github.com/astral-sh/uv/issues/17831 that the uv benchmark had significantly regressed so I briefly investigated and as noted in https://github.com/astral-sh/uv/issues/17831#issuecomment-3844186668 the issue is that we're resolving to a different version of a package (python-rapidjson) which takes >10s to build (on my machine) and creates a dramatic difference in the benchmark.

I think that --no-build or --only-binary :all: should be used so you're not including package build time in benchmarks.

Dominant language
Makefile
Stars
50
Forks
15
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lincolnloop/python-package-manager-shootout

All issues in lincolnloop/python-package-manager-shootout

Similar issues

More Performance issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.