From owner-freebsd-smp Wed Nov 12 21:01:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA13978 for smp-outgoing; Wed, 12 Nov 1997 21:01:12 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA13969 for ; Wed, 12 Nov 1997 21:01:09 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id XAA17161; Wed, 12 Nov 1997 23:00:48 -0600 (CST) From: Kevin Day Message-Id: <199711130500.XAA17161@home.dragondata.com> Subject: Re: Heavily loaded SMP server In-Reply-To: <199711130334.WAA28428@source.isd.state.in.us> from "Raymond L. Gilbert" at "Nov 12, 97 10:34:07 pm" To: sfra47@source.isd.state.in.us (Raymond L. Gilbert) Date: Wed, 12 Nov 1997 23:00:48 -0600 (CST) Cc: joe@via.net, smp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Thus it was recorded by the prophets, Joe McGuckin said: > >I`d like to talk to someone who is using their SMP machine for > >heavy duty WWW serving, etc. > > Yeah so would I! Heavy duty WWW serving seems to imply putting SMP in > a *production* environment. I've been running the SMP kernel for > about a month now with few problems (none related to SMP code > specifically), and I'd like to use it as a heavy-duty WWW server but > I'm not sure that running -current on a production system is wise. > Has anyone out there settled on a good, recent SNAP that could > be used for heavy WWW traffic? > One of my machines is now running the 1108-SNAP version of the SMP kernel... Dual Pentium/200's. It's currently running about 30 eggdrops with no problem, for my users, and if it keeps running well this week, we're going to try moving one of the heavier used web pages we host to it. (www.mk4.com). The only problems we've had so far, are 1) Lots of programs are still expecting *.so.2.1 libraries, when all it has are the 3.0's. 2) We had a terrible time getting NIS to work with a 2.x server and a 3.x client. It turned out to be something to do with the libcrypt's, but I never really figured it all out, it just works now. 3) analog takes *longer* to run on a SMP kernel than a standard kernel... I'm still trying to figure that one out. 4) One user actually complained, because he thought gcc was broken, because it was compiling so fast. :) 5) Now I have no excuse to go buy a dual P/II machine. :) All these problems are 3.0 related, not SMP related though... KEvin Day DragonData