Why doesn't django support connection pool?

Question

I wonder why django doesn't support connection pool? I can't bear open/close connection every request. I try to solve it, but hasn't a good solution.

I try to use mysql_pool, but fail:

TypeError: init() takes exactly 1 argument (3 given)

`__init__` expects only 1 argument and you're passing 3, why? — shahjapan, Dec 28 '10 at 13:03
Are you running django as CGI (instead of something like as WSGI or mod_python)? — Paulo Scardine, Dec 28 '10 at 18:13

score 13 · Answer 1 · edited May 23 '17 at 12:18

13

EDITED: look at Django persistent database connection (feature introduced in 1.6).

Persistent connections avoid the overhead of re-establishing a connection to the database in each request. They’re controlled by the CONN_MAX_AGE parameter which defines the maximum lifetime of a connection. It can be set independently for each database.

edited May 23 '17 at 12:18

Community

1
1

answered Dec 28 '10 at 18:21

Paulo Scardine

73,447
11
124
153

It will. Django explicitly closes connection on end of request. – Suor Oct 03 '11 at 08:33
@Suor: It will indeed - shame on me. – Paulo Scardine Dec 05 '11 at 08:05

score 12 · Answer 2 · answered Oct 19 '14 at 12:25

12

Here's a discussion about why django did not add pooling to the core: https://groups.google.com/forum/#!topic/django-developers/NwY9CHM4xpU

Generally speaking it's because third party applications such as pgbouncer do it better.

answered Oct 19 '14 at 12:25

the_drow

18,571
25
126
193

2

Awesome answer. Btw [Posgres wiki](https://wiki.postgresql.org/wiki/Number_Of_Database_Connections) tells: "Some client side software (like Java EE / JPA / Hibernate) always pools connections, so built-in pooling in PostgreSQL would then be wasteful duplication." – Abdur-Rahmaan Janhangeer Jan 07 '21 at 19:20

Why doesn't django support connection pool?

2 Answers2

Linked