==================
- Drop support for Python 3.4.
- Add support for Python 3.7.
- The timing loops have been rewritten on top of `pyperf
<https://pyperf.readthedocs.io/en/latest/index.html>`_. This
produces much more reliable/stable, meaningful data with a richer set of
statistics information captured, and the ability to do analysis and
comparisons on data files captured after a run is complete. Some
command line options have changed as a result of this, and the
output no longer is in terms of "objects per second" but how long a
particular loop operation takes. See :issue:`37` and :issue:`35`.
- The timing data for in-process concurrency (gevent and threads)
attempts to take the concurrency into account to produce more
accurate results. See :issue:`38`.
- Add debug logging when we think we detect gevent-cooperative and
gevent-unaware databases in gevent mode.
- Add the ability to specify only certain subsets of benchmarks to run
on the command line. In particular, if you've already run the
``add`` benchmark once, you can run other benchmarks such as the
``cold`` benchmark again independently as many times as you want (as
long as you don't ``zap`` the database; that's not allowed).
- The benchmarks more carefully verify that they tested what they
wanted to. For example, they check that their Connection's load count
matches what it should be (0 in the case of the "steamin" test).
- Profiling in gevent mode captures the entire set of data in a single
file. See :issue:`33`.
- The ``--zap`` option accepts a ``force`` argument to eliminate the
prompts. See :issue:`36`.
- Multi-threaded runs handle exceptions and signals more reliably.
Partial fix for :issue:`26`.
- Shared thread read tests clear the caches of connections and the
database in a more controlled way, more closely modeling the
expected behaviour. Previously the cache clearing was
non-deterministic. See :issue:`28`.
- When using gevent, use its Event and Queue implementations for
better cooperation with the event loop.
- Add ``--min-objects`` option to ensure that the underlying database
has at least a set number of objects in place. This lets us test
scaling issues and be more repeatable. This is tested with
FileStorage, ZEO, and RelStorage (RelStorage 2.1a2 or later is
needed for accurate results; earlier versions will add new objects
each time, resulting in database growth).
- Remove the unmaintained buildout configuration. See :issue:`25`.
- Add an option to test the performance of blob storage. See
:issue:`29`.
- Add support for zapping file storages. See :issue:`43`.
- When zapping, do so right before running the 'add' benchmark. This
ensures that the databases are all the same size even when the same
underlying storage (e.g., MySQL databas) is used multiple times in a
configuration. Previously, the second and further uses of the same
storage would not be zapped and so would grow with the data from the
previous contender tests. See :issue:`42`.
- Add a benchmark for empty transaction commits. This tests the
storage synchronization --- in RelStorage, it tests polling the
RDBMS for invalidations. See :issue:`41`.
- Add support for using `vmprof <https://vmprof.readthedocs.io>`_ to
profile, instead of :mod:`cProfile`. See :issue:`34`.