On Tue, 2007-06-19 at 06:51 +0100, David Reynolds wrote: > Morning, > > We are experiencing a problem with Mysql with django. Since an svn > up yesterday (which seems to be revision 5492) we have lots of > sleeping (hanging) mysql processes and we keep hitting our limit of > processes (which we weren't doing before). Anyone have any idea why > it may be doing this? > > Versions: > > apache 2.0.54 > mysql 4.0.24 > mysqldb 1.2.1c2-1 > > If anyone can shed any light, I'd be very interested to know.
It would be interesting to know if anything prior to [5482] (that's 5482, not 5492) works. There was a very large change in [5482] that should be mostly invisible but may have some side-effects we need to be aware of. The details, if you care: template output is now generated via iterators, rather than constructing a huge string and passing the string around. This should be mostly invisible. However, one thing that might be observable is that functions which are called to generate the template may not necessarily be called until the data is being sent back to the client. Ticket #4612, for example, shows how this can be a bit subtle in middleware (not actually a bug, just some experience gained). Now, I have no idea if this is affecting you, but off the top of my head, that is the biggest change we have pushed out lately. I can't think of any MySQL specific changes, but I'm getting old and my memory is failing sometimes, so maybe I've forgotten something. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
