Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 43354 invoked from network); 1 Mar 2005 14:16:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 1 Mar 2005 14:16:30 -0000 Received: (qmail 56809 invoked by uid 500); 1 Mar 2005 14:16:27 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 56379 invoked by uid 500); 1 Mar 2005 14:16:25 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 56364 invoked by uid 99); 1 Mar 2005 14:16:25 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=SPF_HELO_PASS,TO_ADDRESS_EQ_REAL X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from smtp.istop.com (HELO smtp.istop.com) (66.11.167.126) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Mar 2005 06:16:24 -0800 Received: from ns.istop.com (ns.istop.com [66.11.168.199]) by smtp.istop.com (Postfix) with ESMTP id C6DDA2B3B3 for ; Tue, 1 Mar 2005 09:26:53 -0500 (EST) Date: Tue, 1 Mar 2005 09:16:21 -0500 (EST) From: Jeffrey Burgoyne X-X-Sender: burgoyne@ns.istop.com To: "dev@httpd.apache.org" Subject: Re: Puzzling News In-Reply-To: <42247545.1020708@web.turner.com> Message-ID: References: <6.2.1.2.2.20050228142137.07737eb0@pop3.rowe-clan.net> <20050228210955.23366.qmail@mail.infinology.com> <20050228213119.76512.qmail@mail.infinology.com> <3CB607E8DB33278662A59680@st-augustin.ics.uci.edu> <42247545.1020708@web.turner.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N But how many people really need 10,000+ concurrent connections? Obviously CNN does. I'll make a bet Amazon does. Lets add ebay. Those are power users. The web site I manage does about 5 million hits per day (not including graphics, style sheets, etc which are served by a different server), 80% of which are in a ten hour window. Thats 400,000 per hour, 7000 per minute. Thats about 100 hits per second. Average delivery time is running about 1 second on it per hit or so, and we see a need to run about 150 preforks during peak times. Now what percentage of installations see more then 5 million hits per day? I'd dare say it is pretty small. I'd also wager a godo cold ale that the larger sites also have a decent level of expertise to tune their whole system to betetr handle their load. In ym case I realized an issue with the URI translation phase was causing issues, and one week and one apache module later I reduced the number of Apache pre forks required by 70% and reduced the latency time by 60%. Those numbers are both above what 2.0 would have bought me with less work. It wouldn't suprise me if many sites are in the same boat. Those with eough hits to justify a move to 2.0 likely have a higher level of expertise that would allow for a better understanding ofApache and better tuning to provide maximum performance. Jeffrey Burgoyne Chief Technology Architect KCSI Keenuh Consulting Services Inc burgoyne@keenuh.com On Tue, 1 Mar 2005, Brian Akins wrote: > Justin Erenkrantz wrote: > > --On Monday, February 28, 2005 6:24 PM -0500 Jeffrey Burgoyne > > > I believe 255 concurrent clients is really low now-a-days for high-end > > production servers. > > It's when you start to get into several thousand concurrent connections > > that I've found that the memory model of prefork starts to get painful. > > We have run 10,000 + threads on our webservers routinely. Can't do that > with 1.x > > > -- > Brian Akins > Lead Systems Engineer > CNN Internet Technologies >