2009/9/20 Cal Leeming <[email protected]>: > Hi all, > > I've come across an extremely nasty bug in the mpm-peruser. It's caused > so many problems, that I've had to drop it from our production servers. > It would appear, that in a load test of 5000 requests on a static file, > half of the requests are being 503'd... > > For a small server, it's good, but for a large scale production, it's > not cutting it :(
I'm guessing because You didn't provide any meaningfull information. It's not a bug it's a feature, peruser is targeted for shared hosting providing good separation of users performance and security wise. In configuration each processor has MaxProcessors directive whitch sets max number of simultanous connections being served. If your tests require more then MaxProcessors concurrent connections you will get 503 errors. You can raise MaxProcessors or go with some other config if You don't need the separation that peruser provides. >>> - if the multiplexer cannot pass the request to the processor, then it >>> will respond to the client with error "503 Service unavailable" (only >>> works when multiplexer isn't directly passing the socket, eg when >>> SSL is >>> not enabled and NameVirtualhost is set). -- Lazy _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
