Hi Taavi, Unfortunatly - I've now purged the production servers of peruser, so I can't do any further testing :(
However - I can tell you the commands used to replicate the issue: siege -c 2000 http://sitegoeshere.com/staticfilegoeshere.ext and ab -n 2000 -c 20000 http://sitegoeshere.com/staticfilegoeshere.ext OR ab -n 20000 -c 2000 http://sitegoeshere.com/staticfilegoeshere.ext If I recall correctly, the error logs reported no errors. HOWEVER!! There was also something else rather weird.. For the first 16000 requests, the server was as fast as lightening, with little 503's... Then, randomly, after 16000k requests, the entire apache2 server would stop answering any requests or accepting connections on port 80.. I enabled debugging in the peruser module, and when this happened, the debug would just freeze.. then, after 10-20 seconds, something would kick fire it back into action, and it would purge its previous request pool, and start accepting the connections again.. it was VERY weird.. I tried changing the timeout before, and it worked, but the time it took to process the requests was not very nice.. Also - the 503's would still appear.. The best way to replicate this issue, is just use the peruser config I pasted before, then try sending 2000 queries per second with ab, and you'll see what I mean. I've outruled it being a hardware issue, as I've been able to make Zeus Load Balancer combined with Zeus Web Server process 6000+ requests per second, using a reverse SSL proxy on the load balancer... Foxx/Cal Original Message: ----------------- From: Taavi Sannik [email protected] Date: Mon, 21 Sep 2009 12:54:32 +0300 To: [email protected] Subject: Re: [peruser] Peruser 0.4.0 beta 1 [email protected] wrote: > I had set maxprocessors to as much as 5000. And configured the timeout to > ensure nothing > would timeout... Trust me, I got the configuration right, I have previously > spent hours > and hours looking through the source code and practically know peruser > inside out. I even > added my own debug, to try and figure out where it was dying, but to no use > :/ > Hello! The server should only reply with a 503 message when there are no processors available - you can try disabling that check by setting ProcessorWaitTimeout to 0. Also some more questions: - Does the benchmark create any error messages in the error log? - Could you please provide us with the output from ab and the command line invoked. - Are you using any connection/bandwidth limiting modules? -- Taavi Sannik DataCode OY _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser -------------------------------------------------------------------- mail2web.com – Enhanced email for the mobile individual based on Microsoft® Exchange - http://link.mail2web.com/Personal/EnhancedEmail _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
