Faster Python, beyond semantic interposition
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- devops, performance
Research direction
Start by reproducing the reported pystone results with Docker and Podman across the Fedora, Ubuntu, Debian slim, and Conda-Forge images listed in the issue. Compare the Python runtime and image conditions that differ between those runs. Done means identifying a specific, reproducible cause of the performance gap and documenting an actionable improvement.
Written by the indexing model from the issue text.
Description
#501 has a useful suggestion for speeding up Python by ~20%. After that's done, it's actually possible to do better.
Host is Fedora 33. All tests were run with Python 3.9.
On host:
- Fedora's Python gives 200K pystone/sec.
- Conda-Forge Python gives 240K pystone/sec.
Running inside Docker 20.04 (cgroups v2 enabled):
- fedora:33 gives 173K pystone/sec.
- python:3.9-slim-buster, I get 169K pystone/sec.
- ubuntu:20.04 (no shared library): 183K pystone/sec.
- continuumio/miniconda3 with Python from Conda-Forge: 189K/sec
I am mystified why things are so much slower inside Docker. Some of this is clearly not because of the image, but the runtime. But notice the Ubuntu image is definitely faster.
With podman:
- python:3.9-slim-buster: 204K/sec
- continuumio/miniconda3 with Python from Conda-Forge: 230K/sec
Note that the Anaconda (default Conda) Python 3.9 does not appear faster, it's specifically whatever Conda-Forge does. I am trying to figure that out.
- Dominant language
- Dockerfile
- Stars
- 2.8k
- Forks
- 1.1k
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker-library/python
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
docker-library/python#1080 · 8 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
docker-library/python#1121 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
docker-library/python#1082 · 10 comments · 36 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
docker-library/python#1076 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
docker-library/python#1071 · 7 comments ·
All issues in docker-library/python
Similar issues
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/prow#953 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
automated-analysis bug memory-safety
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area/entangle bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100