Analysis updated 2026-07-07 · repo last pushed 2026-07-01
Run before and after benchmarks to check if changes to Python internals make real-world programs faster.
Compare performance across different Python implementations like CPython and PyPy.
Validate that a rewritten Python subsystem actually improves speed on everyday workloads.
| python/pyperformance | google-research/tabfm | lyra81604/zhengxi-views | |
|---|---|---|---|
| Stars | 1,021 | 1,041 | 1,151 |
| Language | Python | Python | Python |
| Last pushed | 2026-07-01 | 2026-07-03 | 2026-06-30 |
| Maintenance | Active | Active | Active |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 3/5 | 3/5 |
| Audience | developer | data | researcher |
Figures from each repo's GitHub metadata at analysis time.
Install via pip and run from the command line, no external infrastructure required.
Pyperformance is a benchmark suite for Python, a standardized set of tests that measures how fast Python code runs. It exists so that anyone working on Python itself (or building alternative versions of Python) can check whether their changes make the language faster, slower, or about the same. The suite focuses on real-world workloads rather than synthetic tests. That means it runs actual applications and common tasks to see how Python handles them, instead of using artificial loops designed just to stress the system. The goal is to give a trustworthy, apples-to-apples comparison across different Python implementations, so a team can say with confidence whether their new version is genuinely faster in practice. The people who would use this are mostly Python core developers and anyone building or maintaining an alternative Python runtime (like CPython, PyPy, or others). For example, if a developer rewrites part of Python's internals to speed up function calls, they can run the benchmark before and after to see if real-world programs actually got faster. It is less relevant to everyday app developers, who typically care about their own code's performance rather than the language engine itself. One notable caveat: the project states it is not yet tuned for PyPy, an alternative Python implementation known for speed. If you want to benchmark PyPy specifically, the README points you to a separate benchmarks project for that. Beyond that, the README is fairly sparse, it does not list which specific benchmarks are included or how long a typical run takes, so you would need to dig into the documentation for those details.
A standardized benchmark suite that measures how fast Python code runs using real-world workloads, so developers working on Python itself can see if their changes make the language faster or slower.
Mainly Python. The stack also includes Python.
Active — commit in last 30 days (last push 2026-07-01).
No license information is provided in the explanation, so the licensing terms are unknown.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.