Opened 15 years ago

Closed 15 years ago

#11798 closed (wontfix)

Django persistent psycopg2 database connection

Reported by: Mike Tkachuk <mike@…> 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


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 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) (1.1 KB ) - added by Mike Tkachuk <mike@…> 15 years ago.

Download all attachments as: .zip

Change History (2)

by Mike Tkachuk <mike@…>, 15 years ago

Attachment: added

comment:1 by Alex Gaynor, 15 years ago

Resolution: wontfix
Status: newclosed

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.

Note: See TracTickets for help on using tickets.
Back to Top