Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 27246 invoked by uid 500); 10 Aug 2000 13:22:56 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 27155 invoked from network); 10 Aug 2000 13:22:50 -0000 Message-ID: <3992B610.D0CC235B@sharp.fm> Date: Thu, 10 Aug 2000 14:03:13 +0000 From: Graham Leggett X-Mailer: Mozilla 4.73 (Macintosh; U; PPC) X-Accept-Language: en,pdf MIME-Version: 1.0 To: new-httpd@apache.org, Hao Sun Subject: Re: [Fwd: apache web server and proxy throughput numbers] References: <3991AD1D.84F744CC@Golux.Com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hi, > Have any of you know anything about apache server/proxy throughput > performance? We did some test and found apache proxy can only do 10 > request per second with freeBSD running on a Pentium 2 500M Hz, 500M main > memory machine with 20 initial apache processes. Do you have anything > better than 10/sec? What configuration are you using the proxy server in? A forward proxy, or a reverse proxy? Also remember that the proxy can only ship data to you as fast as the origin server gives it to you at. It also depends on whether the data you are shipping is cacheable by the proxy or not. We were using the reverse proxy to front end most of the content that lives at http://www.ericsson.se (about 6GB worth of websites on a number of backend machines). The reverse proxy was running on a Solaris E250 machine with 512MB RAM and was shipping around 1-1.5mbps of data at any given time. The number of processes used hovered at around 100 to 150 at any given time, although sometimes it did go higher than that. Regards, Graham --