PEP 683: Update the Perf Regression With the Final Benchmark Results (#3519)
This commit is contained in:
parent
6aeaba7f23
commit
12e276545d
|
@ -230,20 +230,17 @@ those described above in `Motivation`_, reflect this improvement.
|
|||
Performance
|
||||
-----------
|
||||
|
||||
A naive implementation shows `a 4% slowdown`_. We have demonstrated
|
||||
a return to ~performance-neutral~ with a handful of basic mitigations
|
||||
applied. See the `mitigations`_ section below.
|
||||
A naive implementation shows `a 2% slowdown`_ (3% with MSVC).
|
||||
We have demonstrated a return to ~performance-neutral~ with a handful
|
||||
of basic mitigations applied. See the `mitigations`_ section below.
|
||||
|
||||
.. _a 2% slowdown: https://github.com/python/cpython/pull/19474#issuecomment-1502245844
|
||||
|
||||
On the positive side, immortal objects save a significant amount of
|
||||
memory when used `with a pre-fork model <Facebook>`_. Also, immortal
|
||||
objects provide opportunities for specialization in the eval loop that
|
||||
would improve performance.
|
||||
|
||||
.. _a 4% slowdown: https://github.com/python/cpython/pull/19474#issuecomment-1032944709
|
||||
|
||||
TODO: Update the performance impact for the latest branch
|
||||
(both for GCC and for clang).
|
||||
|
||||
Backward Compatibility
|
||||
----------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue