Skip to content
Snippets Groups Projects
Commit 1bb1800c authored by Armin Rigo's avatar Armin Rigo
Browse files

Tweaks to the preamble, answering more directly the question

"yes, it's a PyPy without the GIL".
parent eea549ad
No related branches found
No related tags found
No related merge requests found
......@@ -49,5 +49,6 @@
We achieved – or overachieved – most goals laid out in the first call by
a large margin, while at the same time raising only about half the
money. The result of this first step is `described in the documentation
of PyPy`__.
of PyPy`__. It is a PyPy without the GIL. In the best (artificial)
examples, it runs only 30% slower than a regular PyPy with the JIT.
......@@ -53,6 +54,8 @@
The present proposal is about development of the second half: starting
from the various missing low-level optimizations, it will most
The present proposal is about development of the second half: first,
fixing the various missing low-level optimizations (aiming for this
25%-30% figure, but for most cases rather than only special examples).
Then it will most
importantly focus on developing the Python-facing interface. This
includes both internal things (e.g. do dictionaries need to be more
TM-friendly in general?) as well as directly visible things (e.g. some
......@@ -56,8 +59,9 @@
importantly focus on developing the Python-facing interface. This
includes both internal things (e.g. do dictionaries need to be more
TM-friendly in general?) as well as directly visible things (e.g. some
profiler-like interface to explore common conflicts in a program). It
also includes exploring and tweaking some existing libraries to improve
profiler-like interface to explore common conflicts in a program).
Finally, the third part is
exploring and tweaking some existing libraries to improve
their TM-friendliness (e.g. Twisted and Stackless).
See also the `update on HTM`_ below.
......
......@@ -80,9 +80,12 @@
<p>We achieved – or overachieved – most goals laid out in the first call by
a large margin, while at the same time raising only about half the
money. The result of this first step is <a class="reference external" href="https://pypy.readthedocs.org/en/latest/stm.html">described in the documentation
of PyPy</a>.</p>
<p>The present proposal is about development of the second half: starting
from the various missing low-level optimizations, it will most
of PyPy</a>. It is a PyPy without the GIL. In the best (artificial)
examples, it runs only 30% slower than a regular PyPy with the JIT.</p>
<p>The present proposal is about development of the second half: first,
fixing the various missing low-level optimizations (aiming for this
25%-30% figure, but for most cases rather than only special examples).
Then it will most
importantly focus on developing the Python-facing interface. This
includes both internal things (e.g. do dictionaries need to be more
TM-friendly in general?) as well as directly visible things (e.g. some
......@@ -86,8 +89,9 @@
importantly focus on developing the Python-facing interface. This
includes both internal things (e.g. do dictionaries need to be more
TM-friendly in general?) as well as directly visible things (e.g. some
profiler-like interface to explore common conflicts in a program). It
also includes exploring and tweaking some existing libraries to improve
profiler-like interface to explore common conflicts in a program).
Finally, the third part is
exploring and tweaking some existing libraries to improve
their TM-friendliness (e.g. Twisted and Stackless).</p>
<p>See also the <a class="reference internal" href="#update-on-htm">update on HTM</a> below.</p>
</div>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment