[pypy-commit] extradoc extradoc: integrate arigo's suggestions
antocuni
pypy.commits at gmail.com
Thu Jan 3 08:04:51 EST 2019
Author: Antonio Cuni <anto.cuni at gmail.com>
Branch: extradoc
Changeset: r5932:2d7750cef08d
Date: 2019-01-03 14:04 +0100
http://bitbucket.org/pypy/extradoc/changeset/2d7750cef08d/
Log: integrate arigo's suggestions
diff --git a/blog/draft/2018-12-gc-disable/gc-disable.rst b/blog/draft/2018-12-gc-disable/gc-disable.rst
--- a/blog/draft/2018-12-gc-disable/gc-disable.rst
+++ b/blog/draft/2018-12-gc-disable/gc-disable.rst
@@ -5,7 +5,9 @@
which are useful when you need to respond to certain events with the lowest
possible latency. This work has been kindly sponsored by `Gambit Research`_
(which, by the way, is a very cool and geeky place where to work_, in case you
-are interested).
+are interested). Note also that this is a very specialized use case, so these
+features might not be useful for the average PyPy user, unless you have the
+same problems as described here.
The PyPy VM manages memory using a generational, moving Garbage Collector.
Periodically, the GC scans the whole heap to find unreachable objects and
@@ -96,9 +98,15 @@
better. There is still one spike towards the end, but after some investigation
we concluded that it was **not** caused by the GC.
+Note that this does **not** mean that the whole program became magically
+faster: we simply moved the GC pauses in some other place which is **not**
+shown in the graph: in this specific use case this technique was useful
+because it allowed us to shift the GC work in places where pauses are more
+acceptable.
+
All in all, a pretty big success, I think. These functionalities are already
available in the nightly builds of PyPy, and will be included in the next
-release: take this as a Christmas present :)
+release: take this as a New Year present :)
Antonio Cuni and the PyPy team
More information about the pypy-commit
mailing list