> -----Original Message----- > From: shrike-list-bounces@xxxxxxxxxx > [mailto:shrike-list-bounces@xxxxxxxxxx]On Behalf Of Arjan van de Ven > Sent: Wednesday, March 31, 2004 12:29 AM > To: Roger > Cc: Discussion of Red Hat Linux 9 (Shrike) > Subject: Re: Apache Benchmark - static HTML Results Question > > > > On Tue, Mar 30, 2004 at 08:06:45AM -0800, Roger wrote: > > > > Around Tue, Mar 30, 2004 at 09:43:45AM +0200, Arjan van de > Ven, wrote: > > > > > > > Isn't this _slow_??? I mean, look at the numbers and > the difference > > > > in specs between the server and my laptop! > > > > > > > > In the article, the writer uses a 2x3.2GHz Xeon and > gets up to 4730 > > > > requests/sec!! > > > > > > -c 1000 spawns a lot of parallel work for both the client > app and the > > > server, so you basically kill your performance context > switching... > > > > > > also the number of requests you do is equal to the number > of threads so > > > each thread only does 1 request, with the result that > that 1 request > > > gets the full setup hit of such a thread.... > > I tried my desktop with ab -n 1000 -c 200 http://localhost > > returned: 47.3 requests/s > > Rerunning with: > > ab -n 1000 -c 100 http://localhost > > returns: 1858.95 requests/s > > so that's a pretty strong performance knee between 100 and > 200... what is > the max thread count you've set for apache ? ;) On a stock RH9 apache setup, I think the max thread count is 150 right?? =====httpd.conf==== StartServer 8 MinSpareServers 5 MaxSpareServers 20 MaxClients 150 MaxRequestsPerChild 100 ========================= Changing MaxClients 256 (This is somehow the max that can be inputted using redhat-config-httpd (or something like that) -c 1000 yielded 53.69 requests/sec -c 100 yielded 1020.12 requests/sec -c 256 yielded 75.78 requests/sec vs MaxClient 150 -c 1000 yielded 53.47 request/sec -c 100 yielded 260.35 requests/sec So.. What's happening here? -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list