Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
pypy.org
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
PyPy
pypy.org
Commits
d0cf8619
Commit
d0cf8619
authored
13 years ago
by
Maciej Fijalkowski
Browse files
Options
Downloads
Patches
Plain Diff
write a draft of performance dissemination
parent
bd50ca02
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
source/performance.txt
+43
-0
43 additions, 0 deletions
source/performance.txt
with
43 additions
and
0 deletions
source/performance.txt
0 → 100644
+
43
−
0
View file @
d0cf8619
One of the goals of the PyPy project is to provide a fast and compliant python
interpreter. Part of the way we achieve this is to provide a high-performance
garbage collector and a high performance JIT. Results of comparing PyPy and
CPython can be found on the `speed website`_. Those benchmarks are not a random
collection. They're a combination of real-world Python programs, benchmarks
originally included and benchmarks we found PyPy to be slow on. Consult
descriptions of each for details.
JIT is however not a magic bullet. There are several characteristics that might
be surprising for people having first encounter with it. JIT is generally good
at speeding up straightforward python code that spends a lot of time in
the bytecode dispatch loop, numerics, heave oo etc. When JIT does not help,
PyPy is generally slower than CPython, those things include:
* **Tests**: Ideal unit tests would execute each piece of tested code which
leaves no time for the JIT to warm up.
* **Really short-running scripts**: A rule of thumb is if something runs below
0.2s JIT has no chance, but it depends a lot on the program in question. In
general, make sure you warm up your program before running benchmarks if
you're measuring something long-running like a server.
* **Functions in runtime**: Functions that take significant time in runtime.
PyPy's runtime is generally not as optimized as CPython's and expect those
functions to take somewhere between same time as CPython to 2x longer.
XXX explain exactly what runtime is
Unrelated things that we know PyPy is slow at (note that we're probably working
on it):
* **Long integers**
* **Building very large dicts**
XXX
We generally consider things that are slower on PyPy than CPython PyPy's bugs.
In case you find a thing that's not documented here, report it to our
`bug tracker`_ for investigation
.. _`bug tracker`: http://bugs.pypy.org
.. _`speed website`: http://speed.pypy.org
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment