iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 744: fix broken links to benchmarking-public images (GH-3953)

This commit is contained in:
Andy Castille 2024-09-12 13:31:23 -07:00 committed by GitHub
parent 507d0e53a3
commit 256b644fb3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
peps/pep-0744.rst
View File

@ -501,7 +501,7 @@ Speed
----- -----
Currently, the JIT is `about as fast as the existing specializing interpreter Currently, the JIT is `about as fast as the existing specializing interpreter
<https://github.com/faster-cpython/benchmarking-public/blob/main/configs.png>`__ <https://github.com/faster-cpython/benchmarking-public/blob/main/configs.svg>`__
on most platforms. Improving this is obviously a top priority at this point, on most platforms. Improving this is obviously a top priority at this point,
since providing a significant performance gain is the entire motivation for since providing a significant performance gain is the entire motivation for
having a JIT at all. A number of proposed improvements are already underway, and having a JIT at all. A number of proposed improvements are already underway, and
@ -515,7 +515,7 @@ Because it allocates additional memory for executable machine code, the JIT does
use more memory than the existing interpreter at runtime. According to the use more memory than the existing interpreter at runtime. According to the
official benchmarks, the JIT currently uses about `10-20% more memory than the official benchmarks, the JIT currently uses about `10-20% more memory than the
base interpreter base interpreter
<https://github.com/faster-cpython/benchmarking-public/blob/main/memory_configs.png>`__. <https://github.com/faster-cpython/benchmarking-public/blob/main/memory_configs.svg>`__.
The upper end of this range is due to ``aarch64-apple-darwin``, which has larger The upper end of this range is due to ``aarch64-apple-darwin``, which has larger
page sizes (and thus, a larger minimum allocation granularity). page sizes (and thus, a larger minimum allocation granularity).