Question

我正在运行一个多租户网站，我希望减少每个请求创建PostgreSQL连接的开销。 Django的CONN_MAX_AGE允许这样做，代价是创建了许多与PostgreSQL的开放空闲连接（8个工作者* 20个线程= 160个连接）。每个连接10MB，这会占用大量内存。

主要目的是减少连接时间开销。因此我的问题是：

我应该使用哪种设置来解决此问题？（PgBouncer？）
我可以使用＆＃39;交易＆＃39; Django的游泳池模式？
我会更好地使用像https://github.com/kennethreitz/django-postgrespool这样的东西而不是Django的汇集吗？

Django 1.6设置：

DATABASES['default'] = {
    'ENGINE':   'django.db.backends.postgresql_psycopg2',

     ....

    'PORT': '6432'
    'OPTIONS': {'autocommit': True,},
    'CONN_MAX_AGE': 300,
}

ATOMIC_REQUESTS = False   # default

Postgres的：

max_connections = 100

PgBouncer：

pool_mode = session     # Can this be transaction?
max_client_conn = 400   # Should this match postgres max_connections?
default_pool_size = 20
reserve_pool_size = 5

Answer 1

这是我用过的设置。

pgbouncer在与gunicorn，芹菜等相同的机器上运行。

pgbouncer.ini：

[databases]
<dbname> = host=<dbhost> port=<dbport> dbname=<dbname>

[pgbouncer]
: your app will need filesystem permissions to this unix socket
unix_socket_dir = /var/run/postgresql
; you'll need to configure this file with username/password pairs you plan on
; connecting with.
auth_file = /etc/pgbouncer/userlist.txt

; "session" resulted in atrocious performance for us. I think
; "statement" prevents transactions from working.
pool_mode = transaction

; you'll probably want to change default_pool_size. take the max number of
; connections for your postgresql server, and divide that by the number of
; pgbouncer instances that will be conecting to it, then subtract a few
; connections so you can still connect to PG as an admin if something goes wrong.
; you may then need to adjust min_pool_size and reserve_pool_size accordingly.
default_pool_size = 50
min_pool_size = 10
reserve_pool_size = 10
reserve_pool_timeout = 2
; I was using gunicorn + eventlet, which is why this is so high. It
; needs to be high enough to accommodate all the persistent connections we're
; going to allow from Django & other apps.
max_client_conn = 1000
...

/etc/pgbouncer/userlist.txt：

"<dbuser>" "<dbpassword>"

Django settings.py：

...
DATABASES = {
    'default': {
        'ENGINE': 'django.contrib.gis.db.backends.postgresql_psycopg2',
        'NAME': '<dbname>',
        'USER': '<dbuser>',
        'PASSWORD': '<dbpassword>',
        'HOST': '/var/run/postgresql',
        'PORT': '',
        'CONN_MAX_AGE': None,  # Set to None for persistent connections
    }
}
...

如果我没记错的话，你可以基本上与pgbouncer建立任意数量的“持久”连接，因为当Django完成后，pgbouncer会将服务器连接释放回池中（只要你使用transaction或statement为pool_mode）。当Django尝试重用其持久连接时，pgbouncer负责等待与Postgres的可用连接。

使用Django的CONN_MAX_AGE进行pgbouncer的理想设置

1 个答案: