django-geventpool 1.2.2
Add a DB connection pool using gevent to django (based on django-db-geventpool)
License: Apache 2.0

django-geventpool
====================

.. image:: https://img.shields.io/pypi/v/django-db-geventpool.svg
   :target: https://pypi.python.org/pypi/django-geventpool
   :alt: pypi version

.. image:: http://img.shields.io/pypi/l/django-db-geventpool.svg
   :target: https://github.com/erickponce/django-db-geventpool
   :alt: pypi license

Another DB pool using gevent for PostgreSQL DB (based on django-db-geventpool).

*Need Django 1.5.x or newer (check settings for django >= 1.6)*

Python 3 is supported, but if `gevent` is not installed successfully it will use `eventlet`.


Patch psycopg2
--------------

Before using the pool, psycopg2 must be patched with psycogreen, if you are using `gunicorn webserver <http://www.gunicorn.org/>`_,
a good place is the `post_fork() <http://docs.gunicorn.org/en/latest/settings.html#post-fork>`_ function at the config file:

.. code:: python

   from psycogreen.gevent import patch_psycopg     # use this if you use gevent workers
   from psycogreen.eventlet import patch_psycopg   # use this if you use eventlet workers

   def post_fork(server, worker):
       patch_psycopg()
       worker.log.info("Made Psycopg2 Green")


Settings
---------


  + Set *ENGINE* in your database settings to: 
      + *'django_geventpool.backends.postgresql_psycopg2'*
      + For postgis: *'django_geventpool.backends.postgis'*
  + Add *MAX_CONNS* to *OPTIONS* to set the maximun number of connections allowed to database (default=4)
  + If using django 1.6 or newer, add *'CONN_MAX_AGE': 0* to settings to disable default django persistent connection feature. And read below note if you are manually spawning greenlets 

.. code:: python

    # for django 1.5.x
    DATABASES = {
        'default': {
            'ENGINE': 'django_geventpool.backends.postgresql_psycopg2',
            'NAME': 'db',           # Or path to database file if using sqlite3.
            'USER': 'postgres',                      # Not used with sqlite3.
            'PASSWORD': 'postgres',                  # Not used with sqlite3.
            'HOST': '',                      # Set to empty string for localhost. Not used with sqlite3.
            'PORT': '',                      # Set to empty string for default. Not used with sqlite3.
            'OPTIONS': {
                'MAX_CONNS': 30, # Set max allowed connections
                'CONN_IDLE_TIMEOUT': 60, # Set to auto close idling connections
                'CONN_WAIT_TIMEOUT': 15, # Set timeout when waiting for connections
                'ON_RELEASE_DISCARD_ALL': False # Set True to run DISCARD_ALL when releasing connections
            }
        }
    }

    # for django 1.6 and newer version, CONN_MAX_AGE must be set to 0, or connections will never go back to the pool
    DATABASES = {
        'default': {
            'ENGINE': 'django_geventpool.backends.postgresql_psycopg2',
            'NAME': 'db',
            'USER': 'postgres',
            'PASSWORD': 'postgres',
            'HOST': '',
            'PORT': '',
            'ATOMIC_REQUESTS': False,
            'CONN_MAX_AGE': 0,
            'OPTIONS': {
                'MAX_CONNS': 30, # Set max allowed connections
                'CONN_IDLE_TIMEOUT': 60, # Set to auto close idling connections
                'CONN_WAIT_TIMEOUT': 15, # Set timeout when waiting for connections
                'ON_RELEASE_DISCARD_ALL': False # Set True to run DISCARD_ALL when releasing connections
            }
        }
    }

Using Django 1.6+ ORM when not serving requests
____________

If you are using django 1.6+ with celery (or other), or have code that manually spawn greenlets it will not be sufficient to set CONN_MAX_AGE to 0.
Django only checks for long-live connections when finishing a request - So if you manually spawn a greenlet (or have a task spawning one) its connections will
not get cleaned up and will live until timeout. In production this can cause quite some open connections and while developing it can hamper your tests cases.

To solve it make sure that each greenlet either sends the django.core.signals.request_finished signal or calls django.db.close_old_connections() right before it ends

The decorator method is preferred, but the other alternatives are also valid.

.. code:: python

   from django_db_geventpool.utils import close_connection

   @close_connection
   def greenlet_worker()
        ...

or 

.. code:: python

   from django.core.signals import request_finished
   def greenlet_worker():
      ...
      request_finished.send(sender="greenlet")

or

.. code:: python

   from django.db import close_old_connections
   def greenlet_worker():
      ...
      close_old_connections()


Other pools
------------

* `django-db-pool <https://github.com/gmcguire/django-db-pool>`_
* `django-postgresql <https://github.com/kennethreitz/django-postgrespool>`_