Author: Armin Rigo <[email protected]>
Branch: extradoc
Changeset: r484:1bb1800c3a16
Date: 2014-04-10 10:45 +0200
http://bitbucket.org/pypy/pypy.org/changeset/1bb1800c3a16/

Log:    Tweaks to the preamble, answering more directly the question "yes,
        it's a PyPy without the GIL".

diff --git a/source/tmdonate2.txt b/source/tmdonate2.txt
--- a/source/tmdonate2.txt
+++ b/source/tmdonate2.txt
@@ -49,15 +49,19 @@
 We achieved &#8211; or overachieved &#8211; 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.
 
-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
-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.
diff --git a/tmdonate2.html b/tmdonate2.html
--- a/tmdonate2.html
+++ b/tmdonate2.html
@@ -80,14 +80,18 @@
 <p>We achieved &#8211; or overachieved &#8211; 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
-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>
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to