On Thu, Jul 12, 2012 at 3:37 AM, Anand Agarwal <[email protected]> wrote: > As you know, Django uses new database connection for each request. This > works well initially. However as the load on the server increases, > creating/destroying connections to database starts taking significant amount > of time. You will find many questions about using some kind of connection > pooling for Django on sites likeStackOverflow For example, Django > persistent database connection.
There is a reason that Django doesn't manage connection pooling -- it's because it's handled quite well by third party tools like pgPool. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
