From owner-freebsd-questions@FreeBSD.ORG Thu Jul 13 15:22:05 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EBE816A4DA for ; Thu, 13 Jul 2006 15:22:05 +0000 (UTC) (envelope-from danial_thom@yahoo.com) Received: from web33303.mail.mud.yahoo.com (web33303.mail.mud.yahoo.com [68.142.206.118]) by mx1.FreeBSD.org (Postfix) with SMTP id 989F143D6B for ; Thu, 13 Jul 2006 15:22:04 +0000 (GMT) (envelope-from danial_thom@yahoo.com) Received: (qmail 37934 invoked by uid 60001); 13 Jul 2006 15:22:03 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=BzyAdLNuafnpfyCDi1E2qmOpEWmCb2fjLvg+LyKi1s4ugZDrOl0UFWlmJSytqrcqwqvqiNZ42hFr0HcJdCiMoV3AJhfKBuUzWDlnkPtl7JxmCE4EXDCJ8cysDemiN7ttIVbV9djkdXvzD6Hmew2m/Z7oZrjm/HfCWvfsyVydKto= ; Message-ID: <20060713152203.37932.qmail@web33303.mail.mud.yahoo.com> Received: from [65.34.182.15] by web33303.mail.mud.yahoo.com via HTTP; Thu, 13 Jul 2006 08:22:03 PDT Date: Thu, 13 Jul 2006 08:22:03 -0700 (PDT) From: Danial Thom To: Jerry McAllister In-Reply-To: <200607131436.k6DEa1E6017776@clunix.cl.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-questions@freebsd.org Subject: Re: Are hardware vendors starting to bail on FreeBSD ... ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: danial_thom@yahoo.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 15:22:05 -0000 --- Head in the sand Jerry mumbled: > > --- Francisco Reyes > > wrote: > > > > > Marc G. Fournier writes: > > > > > > > the problem is that none of the Tier 1 > > > hardware manufacturer's support > > > > FreeBSD, and a growing number of places > (ie. > > > Adaptec / Intel) appear to be > > > > dropping support for it as well ... > > > > > > But companies like 3Ware and Areca are > > > supporting it and from what I see on > > > the lists, people are voting with their > money > > > in their favor. > > > > Mainly because they had drivers that required > > little modification from previous versions. > Intel > > has a few other things on their plate, > releasing > > more processors to bail out Freebsd's paltry > > performance, so give them a break. > > > > How long are vendors supposed to wait for the > > FreeBSD developers to deliver the performance > > they've claimed that they can deliver? I know > > several network appliance vendors all stuck > on > > FreeBSD 4, because 5 and 6 are a step > backwards > > performance-wise. Now they're saying 7 will > be > > the one. > > > > FreeBSD is the OS that cried "WOLF", and the > > vendors are starting to ignore the calls. The > > infrastructure is so poor (in terms of > process > > switching times and scheduler efficiencies), > and > > they seem clueless on how to fix it. > > Must be a troll. > FreeBSD performance is not what holds it back. > It competes well with others out there. > > ////jerry No it doesn't, Jerry. Even Robert Watson, who spends most of his time on performance issues, readily admits that - FreeBSD 6 is faster with 1 processor than 2 - FreeBSD 6 is slower with 1 processor than Freebsd 4.x The process switch times are 2-4x slower than on linux. Thats not 2-4%, thats 200-400% slower. Simply enabling SMP on a single processor system adds 20-25% overhead in freebsd 6.1. Again, readily admitted/accepted by the developers. There is no way to recover that in efficiency, at least not for a long time. What's really frightening is that Dragonfly is going to shed the giant lock before Freebsd, and there's only one guy working on it. Its prima facie evidence that IQ isn't cumulative. DT __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com