How does Django's connection pooling and CONN_MAX_AGE setting affect performance? Django की कनेक्शन पूलिंग और CONN_MAX_AGE सेटिंग परफॉर्मेंस को कैसे प्रभावित करती है?

By default, Django opens a new database connection for each request and closes it at the end (CONN_MAX_AGE = 0), which is safe but adds the overhead of a full connection handshake — including authentication and TLS negotiation for remote databases — to every single request.

Setting CONN_MAX_AGE to a positive number of seconds (or None for unlimited) enables persistent connections: a connection is reused across multiple requests as long as it's still valid and hasn't exceeded the max age, avoiding repeated handshake overhead. For high-concurrency deployments, this is often combined with an external connection pooler like PgBouncer in front of PostgreSQL, since Django's built-in persistent connections are per-worker-process, not a true shared pool across all workers.

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql',
        'CONN_MAX_AGE': 60,
        'CONN_HEALTH_CHECKS': True,
    }
}