From owner-freebsd-chat Wed Dec 15 0:15:51 1999 Delivered-To: freebsd-chat@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id CEB7815019 for ; Wed, 15 Dec 1999 00:15:48 -0800 (PST) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id BAA02558; Wed, 15 Dec 1999 01:15:21 -0700 (MST) Message-Id: <4.2.0.58.19991215010917.048dfae0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 15 Dec 1999 01:12:54 -0700 To: David Scheidt From: Brett Glass Subject: Re: dual 400 -> dual 600 worth it? Cc: Jamie Bowden , Terry Lambert , noslenj@swbell.net, chat@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19991214174918.04736140@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:07 PM 12/14/1999 , David Scheidt wrote: > > Multiprocessing has always been a stopgap measure to get extra performance > > out of a machine until uniprocessors caught up. The diminishing returns > >But uniprocessors will never catch up. Actually, uniprocessors often do best in price/performance, because multiprocessor servers are priced so high and CPUs represent such a large precentage of the price of the system. >The glue needed to build an N-way >machine will always be less expensive than N uniprocessor boxes. Not so. The special chip sets are usually priced at a premium. > > make tightly coupled multiprocessing far less desirable than loosely > > coupled (or uncoupled!) distributed computing. > >For some applications loosely coupled multi-processing makes sense. For >others, like operations on one datastream, it doesn't. Actually, a Web page that draws images from several servers via IMG tags is very much like an "operation on one datastream," very neatly distributed. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message