No, the database is pretty standard (mysql 5.1.37-community). This is an 'in-house' tool and we have about 15 consistent users. They hit is pretty heavily and notice this issue during that time, but it also pops up throughout the day. It does seem to be "fixed," albeit temporarily, after we restart apache, but I am not sure if that is a red-herring since it will pop up again fairly quickly.
Before going live we did some basic load testing and did not experience this issue; however, there is a difference between testing and actually using a Web app. On Jul 1, 9:48 am, Tom Evans <tevans...@googlemail.com> wrote: > On Thu, Jul 1, 2010 at 3:41 PM, vjimw <im.a.machobea...@gmail.com> wrote: > > It only happens in our production environment. We have a stage > > environment, which is a mirror of production, that does not have this > > behavior and it does not happen on our development or local > > environments. The trace is a good idea to try to see more > > information. > > Are you doing anything funky with your databases? Read only slaves? > > Cheers > > Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
