tpc_begin(): Get rid of the apply() call since I believe we can now
rely on extended-call syntax being available.

simple free list using a mix of exact-fit and last-fit with a roving
pointer as suggested by Tim.  Use -f to use this version.

Renamed BuddyNode to BlockNode since it is now used by both allocators.

Moved some code around in an attempt to organize it more top-down.

Moved the report printing into the Simulation base class.  Print the
class name and exact cache size before the header; skip the final
report printing if only one previous report was printed.

  Versions:   0 records used a version

1000*1000.  This makes it easier to specify cache sizes for the buddy
system that don't have to be rounded up to the next power of two.  It
does make future reported results incompatible with past results.

allocator.

Different versions of ZODB do different things with the serialnos for
abortVersion().  To be safe and avoid giving non-version data with an
invalid serialno after an abort version, invalidate the version and
non-version data.

This hurts cache effectiveness when a version is aborted, but I expect
it will have little practical impact.

Sort options alphabetically.  Remove dependency between -S, -q and -v
options (-S no longer disables -q and enables -v).  Remove dependency
between -S and -h (histogram is printed regardless of dostats).

in, right, Jeremy? :-)

Repair comments in _call() about how wait() handles reply lock.

# NB: commit() is responsible for calling tpc_begin() on the storage.
# It uses self._begun to track whether it has been called.  When
# self._begun is None, it has not been called.

# This arrangement allows us to handle the special case of a
# transaction with no modified objects.  It is possible for
# registration to be occur unintentionally and for a persistent
# object to compensate by making itself as unchanged.  When this
# happens, it's possible to commit a transaction with no modified
# objects.

# Since tpc_begin() may raise a ReadOnlyError, don't call it if there
# are no objects.  This avoids spurious (?) errors when working with
# a read-only storage.

Add code to handle this in Connection's tpc_begin() and commit()
methods.

Add two tests in testZODB.

An earlier revision (1.68) fixed invalidation code when an object had
no oid (oid == None).  There is no longer anyway to get None in
_invalidated, and it has been a long time since a None there meant
"invalidate everything."

At long last, then, remove all the code deal with the invalidate
everything behavior.

  invalidations instead of only the ones that hit the cache.

- Support reading gzipped files.  This is triggered automatically when
  the filename ends in .gz.  Also support reading from stdin (pass '-'
  as filename).

- Widen the FLIPS column by one to match the EVICTS column width of
  the LRU simulation.

- Support simulating alternative caching strategies.  For now, only
  LRU is supported, triggered by the -l option.

- Change the Simulation base class to store the cachelimit argument.
  (The constructor signature must be the same across all subclasses.)

the filename ends in .gz.  Also support reading from stdin (pass '-'
as filename).

base class.

report overall statistics for all columns.

ZEO_CACHE_TRACE set (see stats.py for file format description).

correct header sizes.

loads and hits and the hit rate is now reported every 15 minutes.

added DanglingReferenceError. A new exception for storages to report the fact that a transaction is storing a reference to an object that does not exist. Doing this is 'a bad thing', although it is not entirely clear that it is prohibited. So far only DirectoryStorage makes this check. This is given its own exception class because some code may be able to catch it, and regenerate the object that the storage thinks does not exist.

p can be negative, which merely means the offset is in the other file.

p can be negative, which merely means the offset is in the other file.

- Always print start and flip events.  Add the newline before the
  stats back.

records).

Report distribution of "current file" bit.

  trace data; first and last timestamp, and their difference in
  seconds; how many records had their version bit set.

 - All large numbers reported are formatted with commas
   (e.g. '1,234,567').