Just to throw my two cents in. My background is high-traffic fantasy sports websites (a different sort of geekness) and I've dealt with connection pooling and connection persistence separately on other ancient platforms. I will +1 Alex's observation that connection pooling and persistent connections are two different things. This problem also has little to do with high-traffic sites and all to do with the normal use cases. I will also +1 that the default to require reconnections is bad enough to be considered a bug. For reasons already stated, this should never be the default longevity of connections.
I implemented the connection pool hack (to get persistent connection) with SQLAchemy using MySQL for an RBS Futbol Soccer game. And I think it's a hack because basically, I had to buy the happy meal (pooling) just to get the collectible toy (persistent connections). Once we decouple connection pooling and persistent connections in our heads... I think this becomes a simpler issue. If you had 50 web threads going and each one had a connection to the database that stays open forever, even at 1am when you have no users, that's not a problem. Even those 50 threads sitting there is not a problem. As a matter of fact, I much prefer to keep those 50 web threads open so Python+Django+My Bloated Code isn't reinstantiated all the time. If you have 1000 connections open, now you might want to have some connection pooling. But that's a separate problem to be solved by a separate package and discussed in a different forum. I do understand this complicates the edge cases where you don't want the connections to stay open and those who want to have connection pooling, but since those are edge cases in my opinion, it should be a little more difficult. I believe the argument is being made that it's not Django's problem if connections are kept alive. It's not a battery that needs to be included. I would argue that this battery needs to be included as it's a problem with moderate and low traffic sites. Including high traffic sites in this discussion only confuses the issue since we're really talking connection pooling for those cases. On Jul 27, 4:43 pm, Glenn Maynard <gl...@zewt.org> wrote: > On Sun, Jul 26, 2009 at 10:17 PM, Amitay Dobo<amit...@gmail.com> wrote: > > So to sum up: I vote up connection pooling. Where do I sign up? > > Thread hijacking. Thanks, always appreciated. > > -- > Glenn Maynard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
