Author: Alex Gaynor <[email protected]>
Branch: extradoc
Changeset: r5075:cfedeaf7332e
Date: 2013-10-14 18:21 +0200
http://bitbucket.org/pypy/extradoc/changeset/cfedeaf7332e/
Log: Some grammar and language tweaks
diff --git a/blog/draft/incremental-gc.rst b/blog/draft/incremental-gc.rst
--- a/blog/draft/incremental-gc.rst
+++ b/blog/draft/incremental-gc.rst
@@ -1,10 +1,9 @@
-
Incremental Garbage Collector in PyPy
=====================================
Hello everyone.
-We're pleased to announce that as of today (so tomorrows nightly),
+We're pleased to announce that as of today (so tomorrow's nightly),
the default PyPy comes with a GC that has much smaller pauses than yesterday.
Let's start with explaining roughly what GC pauses are. In CPython each
@@ -23,19 +22,19 @@
del a
del b
-This creates a reference cycles. It means that while we deleted references to
-``a`` and ``b`` from the current scope, they still have a refcount of 1,
-because they point to each other, while the whole group has no reference
-from the outside. CPython employs a cyclic garbage collector that is used to
-find such cycles. It walks all objects in memory, starting from known roots
-like immortal prebuilt objects, roots on the stack etc. This solves the
-problem, but creates a noticable GC pauses when the heap becomes large and
+This creates a reference cycle. It means that while we deleted references to
+``a`` and ``b`` from the current scope, they still have a reference count of 1,
+because they point to each other, even though the whole group has no references
+from the outside. CPython employs a cyclic garbage collector which is used to
+find such cycles. It walks over all objects in memory, starting from some known
+roots, such as ``type`` objects, variables on the stack, etc. This solves the
+problem, but can create noticable GC pauses as the heap becomes large and
convoluted.
-PyPy has essentially only the cycle finder - it does not bother with reference
-counting, but it walks alive objects every now and then (this is a big
-simplification, PyPy's GC is much more complex than this). It also has
-a problem of GC pauses. To alleviate this problem, which is essential for
+PyPy essentially has only the cycle finder - it does not bother with reference
+counting, instead it walks alive objects every now and then (this is a big
+simplification, PyPy's GC is much more complex than this). As a result it also
+has the problem of GC pauses. To alleviate this problem, which is essential for
applications like games, we started to work on incremental GC, which spreads
the walking of objects and cleaning them across the execution time in smaller
intervals. The work was sponsored by the Raspberry Pi foundation, started
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
