Adjusted documentation about aggregate caching.
@@ -615,14 +615,22 @@ recently used aggregate will be evicted from the cache when it is full.
A value of ``'0'`` will enable an unlimited cache. The default is for
aggregate caching not to be enabled.
-To disable fast-forwarding of caches aggregates, set
-``AGGREGATE_CACHE_FASTFORWARD`` in the application environment to
-a false value as interpreted by :func:`~eventsourcing.utils.strtobool`,
-that is one of: ``'n'``, ``'no'``, ``'f'``, ``'false'``, ``'off'``, or ``'0'``.
-Only do this when there is only one instance of the application is being used
-to evolve the state of the aggregates, otherwise aggregates in the cache will
-become stale and integrity errors will occur when attempting to evolve the state
-of the stale aggregates. The default is for fast-forwarding to be enabled.
+When caches aggregates are accessed, they are "deep copied" to prevent the cache
+being corrupted with aborted changes. When aggregates are succefully saved, the
+cache is updated. Retrieved aggregates are also placed in the cache. To avoid
+using stale aggregates from the cache, for which subsequent events have been
+stored outside of the application instance, cached aggregates are "fast-forwarded"
+with any subsequent events. This involves querying for subsequent events. To disable
+fast-forwarding of cached aggregates, set``AGGREGATE_CACHE_FASTFORWARD`` in the
+application environment to a false value as interpreted by
+:func:`~eventsourcing.utils.strtobool`, that is one of ``'n'``, ``'no'``, ``'f'``,
+``'false'``, ``'off'``, or ``'0'``. Only do this when only one instance of
+the application being used to evolve the state of the aggregates, otherwise
+integrity errors will occur when attempting to evolve the state of stale
+aggregates. The default is for fast-forwarding to be enabled when aggregate
+caching is enabled. But in cases where there is only one application instance,
+greater performance improvement will be obtained by disabling fast-forwarding
+because querying for new events will be avoided.
.. _Persistence:
