gabor wrote: > hmmm..so am i correct when i say, that in a non-multithreaded web-app > definition-2-pools are not needed/ do not help?
Pretty much. The benefit really comes in multi-threaded environments where a new thread is being started for each request. When each of those threads makes its own db connection, you can see how a big traffic spike can be catastrophic -- there's no limit on the number of connections that might be made. With a limited pool of connections, you can at least choose to block or raise an exception when a connection isn't available, so your worst case scenario is a nice error or a slow response, not a dead db server. JP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
