Author: Armin Rigo <ar...@tunes.org>
Branch: stm-gc
Changeset: r54770:1c1ee4c2d200
Date: 2012-04-27 09:56 +0200
http://bitbucket.org/pypy/pypy/changeset/1c1ee4c2d200/
Log: Update docs
diff --git a/lib_pypy/transaction.py b/lib_pypy/transaction.py
--- a/lib_pypy/transaction.py
+++ b/lib_pypy/transaction.py
@@ -113,10 +113,16 @@
is not shared between multiple concurrently-running transactions.
It can be accessed without conflicts.
- It can be used for purely transaction-local data.
+ It can be used for purely transaction-local data that needs to be
+ stored in a single global object. As long as the data is not needed
+ after the transaction, e.g. because it is removed before the
+ transaction ends, using a "local" instance avoids conflicts which
+ would otherwise systematically trigger.
- It can also be used for long-living caches that store values that
- are (1) not too costly to compute and (2) not too memory-hungry,
- because they will end up being computed and stored once per actual
- thread.
+ Values that remain in a "local" instance after the end of a
+ transaction are visible in the next transaction that happens to be
+ executed on the same thread. This can be used for long-living
+ caches that store values that are (1) not too costly to compute,
+ because they will end up being computed once per thread; and (2) not
+ too memory-hungry, because of the replicated storage.
"""
_______________________________________________
pypy-commit mailing list
pypy-commit@python.org
http://mail.python.org/mailman/listinfo/pypy-commit
