From owner-freebsd-questions Mon Aug 28 14:36:32 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (zoom3-006.telepath.com [216.14.3.6]) by hub.freebsd.org (Postfix) with SMTP id 2B60637B42C for ; Mon, 28 Aug 2000 14:36:07 -0700 (PDT) Received: (qmail 97120 invoked by uid 100); 28 Aug 2000 21:35:31 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14762.56098.997893.119112@guru.mired.org> Date: Mon, 28 Aug 2000 16:35:30 -0500 (CDT) To: Alfred Perlstein Cc: questions@freebsd.org Subject: Re: Scaling Apache? In-Reply-To: <17477616@toto.iv> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > * Steve Lewis [000828 11:53] wrote: > > On Mon, 28 Aug 2000, Alfred Perlstein wrote: > > > > What do you recommend for a web server if Apache is "entirely useless" may > > > > I ask? > > > Zues, thttpd, roxen, there's a lot out there that are a lot faster. > > > > > > Supposedly Zues is king. > > Do you happen to know what these do better than apache? > "everything", apache needs a process to handle each request Huh? That stopped being true a *long* time ago. Last time I looked at the default config, the number of requests a process would handle was set very low, but that is trivially fixable. > this doesn't work when you have thousands of connections per-second > it can't even deal with 200-300 per-second. That's fewer requests than one process handles on any reasonable apache config. Apache sucks for lots of reasons, but they killed the single-process-request model quite a while ago. They also do beat the (only marginally better) single-thread-request model. > > I imagine that these faster servers would use the hardware in a way that > > keeps request overhead lower (logging and caching tricks) but the > > trade-offs in server-side scripting support could kill that. If server-side scripting is an issue, I'd seriously recommend looking at Medusa. It uses the fastest model I know of (select-and-dispatch), avoids the strange problems Apache's preforked, multiple-requests-per-child creates with shared objects, comes with a scripting language built in, and is used by at least one high-volume site (egroups, or whatever they're called these days).