Commit ad8f29f0 authored by Jeremy Hylton's avatar Jeremy Hylton

Extend the entry about the new object cache, including notes on the

importance of cache size and the need to recompile extensions for
PER_GHOSTIFY().

Add entries for the Connection change made today and a very generic
entry to describe all the BTrees bugs that Tim has fixed.
parent 41de5166
...@@ -139,7 +139,19 @@ Zope Changes ...@@ -139,7 +139,19 @@ Zope Changes
- Collector #304: several catalog optimisations - Collector #304: several catalog optimisations
- New implementation of ZODB object cache. - New implementation of ZODB object cache. The new
implemenation is more likely to keep the size of the object
cache close to the target size. This change means that memory
consumption may be reduced. Some users will need to increase
the default cache size, because a too small setting is more
likely to hurt performance than it did in the past.
Third-party C extensions that use the persistence API must be
recompiled, and may need to be updated to work correctly with
the new cache; see PER_GHOSTIFY().
- The ZODB Connection is now resposible for registering changed
objects with the current transaction.
- Implementation of RestrictedCreation fishbowl proposal; - Implementation of RestrictedCreation fishbowl proposal;
Product registration can now include a function used to Product registration can now include a function used to
...@@ -629,6 +641,10 @@ Zope Changes ...@@ -629,6 +641,10 @@ Zope Changes
- Fixed conflict resolution problem in BTrees (BTreeTemplace/ - Fixed conflict resolution problem in BTrees (BTreeTemplace/
_p_resolveConflict) _p_resolveConflict)
- Fixed many subtle bugs in the BTrees, including some that
could silently corrupt the BTree and render some data
inaccessible.
- Collector #2524: Medusa sent "HTTP/None..." as response header when - Collector #2524: Medusa sent "HTTP/None..." as response header when
then HTTP version could not be determined from the HTTP request. then HTTP version could not be determined from the HTTP request.
Now sending "HTTP/1.0..." Now sending "HTTP/1.0..."
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment