Hi, On Wed, Jan 16, 2008 at 02:40:52PM -0800, [EMAIL PROTECTED] wrote: > We have recently switched to the worker MPM. We know that while > Django says to use prefork, we've heard from others that worker works > fine in most cases, and due to the high-volume Ajax nature of our > application, worker is the only way we've found to prevent our server > from being overrun during peak use times. However, because worker is > the big thing that has changed recently, and the problem was not > observed before then, it seems a likely suspect.
Seems straight-forward enough. You have two options: * Switch back to prefork and find a different way to scale your performance. * Find the code that is not thread-safe and make it thread-safe. -Forest -- Forest Bond http://www.alittletooquiet.net
signature.asc
Description: Digital signature
