From owner-freebsd-stable Sat Aug 7 14: 9:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 65CC614CFC for ; Sat, 7 Aug 1999 14:09:52 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA22258; Sat, 7 Aug 1999 14:06:25 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AC9FD1.933EBC3D@gorean.org> Date: Sat, 07 Aug 1999 14:06:25 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: tcobb@staff.circle.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: continued crashes with 3.1-Stable References: <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb@staff.circle.net wrote: > > I think the problem is the SMP. I've been having frequent > freezes with SMP under heavy webserver load with 3.2-R, > and 3.2-S. I'm unfortunately led to believe that FreeBSD > SMP is just not ready for primetime. Too bad the $$ we blew > on a dual PIII-550 box. We're having pretty good luck with our dual PIII-500 boxes under pretty heavy webserver load. However for various reasons we're using -current. There are some other factors to consider though. What kind of motherboards and nic cards are you using for example? Also, how heavy is heavy? And what kind of performance tuning have you done with the kernel, etc? It is of course possible that you're experiencing problems with the SMP code, but there are other places to look as well. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message