httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Austin Gonyou <aus...@coremetrics.com>
Subject Re: Saturation stress testing httpd problems
Date Thu, 21 Sep 2000 20:35:46 GMT
That sounds as though you are having a limitation issue with ram or some 
such thing. Something I've seen on Solaris many many times, when it comes 
to apache. I would actually like to see if you could come to the same 
conclusions on Linux. (without your module , unless you'd like to 
recompile for Linux). The main thing here is that I've used AB for quite 
some time and used the hell out of it for creating stress and such on the 
servers. Also Jmeter like a champ too. I've tested both linux and 
solaris, on sparc, and every time, Linux has outperformed solaris on 
sparc for our particular application. We also have custom modules too, so 
I know the development effort you may have put into it. One thing I 
noticed through all my testing though, is there is a tweaking needed for 
that kind of stress. I run only a few servers, 20 - 30, max and then let 
them spawn their asses off. Mainly because I still get a decent amount of 
performance, and I can push my linux boxes to 400-600 concurrent 
connections each before they reach their ulimit, since my module writes 
data. I hope this helps you with some insight.
Austin 

>>>>>>>>>>>>>>>>>> Original Message
<<<<<<<<<<<<<<<<<<

On 9/21/00, 9:57:42 AM, "Bates," Jonathan <Jonathan.Bates@bskyb.com> wrote 
regarding Saturation stress testing httpd problems:


> Hi All,

> I don't know if this is the correct forum for this problem - if not 
please
> let me know of another.

> Here goes..

> We have an infrastructure that uses Apache (latest version) running on a
> server farm of solaris boxes to support (eventually) up to 10 million
> concurrent users (apache is used as a gateway server via our specialist
> module).

> I've written a test program that stresses the server by continuously 
sending
> a number of concurrent requests to Apache (currently configured to run 
200
> or so httpd's).

> When the concurrency exceeds the 200 configured httpds, Apache gets 
swamped
> and falls over. - This I don't mind too much, but after getting swamped 
it
> falls over and doesn't recover - which is a big problem.

> It seems to leave thousands of opened sockets on port 80 with TIME_WAIT
> status - which can be seen via 'netstat -a'.

> The problem doesn't lie in our specialist gateway module as it also 
happens
> in raw Apache.

> Has anyone else encountered this problem, if so do you know of any
> solutions?

> Many Thanks
> Jon Bates
> WAPTV Project
> BSkyB Television Ltd.
> UK.


> **********************************************************************
> Information in this email is confidential and may be privileged.
> It is intended for the addressee only. If you have received it in error,
> please notify the sender immediately and delete it from your system.
> You should not otherwise copy it, retransmit it or use or disclose its
> contents to anyone.
> Thank you for your co-operation.
> **********************************************************************

Mime
View raw message