Try to handle multiple connections better. The session database is a hot spot. When multiple requests (e.g. 20) come in at the same time session database contention can get great. The original code didn't retry session database access when the open failed. This resulted in errors at the client. The second pass delayed 0.01 seconds and retried. It was better but we still had multiple second stalls. I think the first request got in, everybody else backed up and then retried at the same time. Again they stepped on each other. With logging I would see many counters go all the way to low single digits or to -1 indicating falure. This pass uses randomint to generate delays from 0-.125 seconds in 5ms increments. This performs better in testing. I rarely saw a counter less than 13 (2 failed retries). Current logging starts after 6 failures and counts down until success or failure.

=======================================================
Roundup: an Issue-Tracking System for Knowledge Workers
=======================================================

For how to contact the community see https://www.roundup-tracker.org .

Contents
========

.. toctree::
   :maxdepth: 2

   features
   installation
   upgrading
   FAQ
   user_guide
   customizing
   admin_guide
   debugging
   xmlrpc
   rest
   overview
   Design (original) <design>
   developers
   tracker_templates
   Notes about the MySQL Database backend <mysql>
   Notes about the PostgreSQL Database backend <postgresql>
   glossary
   acknowledgements
   Richard Jones implementation notes <implementation>
   license

See: https://wiki.roundup-tracker.org/ReleaseErrata for fixes to
documentation.

Indices
=======
 
* :ref:`genindex`