[re-post] MySQL connection pooling - preferred method??

18 views
Skip to first unread message

Cal Leeming [Simplicity Media Ltd]

unread,
Jan 26, 2012, 3:09:53 PM1/26/12
to django...@googlegroups.com
Hey all,

Not had much luck on this on django-developers, so if anyone else on django-users wants to add their two cents on this thread, that'd be great.

I'm still looking into it, and it looks like the best approach is to create a new MySQL backend with support for connection pooling, but I'm still really dubious because when it gets into those depths, surely that should be in the core... *shrugs*

Penny for your thoughts? :)

Cal

---------- Forwarded message ----------
From: Cal Leeming [Simplicity Media Ltd] <cal.l...@simplicitymedialtd.co.uk>
Date: Wed, Jan 25, 2012 at 12:11 AM
Subject: MySQL connection pooling - preferred method??
To: django-d...@googlegroups.com, Harry Roberts <harry....@simplicitymedialtd.co.uk>


Hi all,

After spending about 30 minutes looking through old tickets, long discussion threads and various blogs, I'm still not clear on the MySQL connection pooling topic.

To quote Russ: "the capability already exists in third party tools, and they're in a position to do a much better job at it than us because it's their sole focus" [3]

Could a core dev (or anyone else with experience on this) clarify which approach is recommended, on the following conditions:

* Safety (should not cause any strangeness with query cache or ORM)
* Performance (should avoid causing Django to open a new database connection on every request)

I found various ways to accomplish this, one of which was to use SQLalchemy[1], another was to stop Django from closing the database connection after each query[2].

I'm hoping this thread will also serve as a final answer for anyone else looking for clarification.

Many thanks

Cal




Reply all
Reply to author
Forward
0 new messages