Opened 15 years ago
Closed 15 years ago
#11798 closed (wontfix)
Django persistent psycopg2 database connection
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Hi folks,
I've strugled with slow performance of django and found that the source is the all time reconnect to database, so I implemented the custom psycopg2 based database engine that improved the performance from 350 to 1600 requests per second (on small page with few SELECTs). To use it
just save the file base.py in any directory (e.g. postgresql_psycopg2_persistent) and set in settings
DATABASE_ENGINE to projectname.postgresql_psycopg2_persistent
Please let me know what you think.
Attachments (1)
Change History (2)
by , 15 years ago
comment:1 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The suggestion for any sort of connection pooling has been rejected several times, if you disagree with this I suggest making your case on the django-developers mailing list, for now closing as wontfix.