Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA86655 for ; Wed, 25 Aug 1999 13:22:47 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id NAA21519; Wed, 25 Aug 1999 13:19:43 -0400 (EDT) From: Bruce Momjian Message-Id: <199908251719.NAA21519@candle.pha.pa.us> Subject: Re: [SQL] 2 million+ entries In-Reply-To: <37C420F2.95BB72E6@nsi.edu> from "G. Anthony Reina" at "Aug 25, 1999 09:59:30 am" To: "G. Anthony Reina" Date: Wed, 25 Aug 1999 13:19:43 -0400 (EDT) CC: Michael Richards , "pgsql-sql@postgreSQL.org" X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Michael Richards wrote: > > > We're currently testing a system with about 1.2 million records with 6.5 > > and it outperforms SQL server 6 by quite a lot. It's running on a dual P3 > > with a 4 9.1 gig Cheetah array on a DPT controller running RAID0. I'm > > pretty happy with it... > > > > > > Great balls of fire! A dual P3 with a four 9.1 Gig RAID0 Cheetah array? > That's fantastic! How much did that set you back? Are there any special > quirks about using Postgres on a multiple processor, multiple disk > system? No quirks. Our multi-Unix-process model for each backend makes multi-cpu's work great. In fact, multi-threading, which mysql uses to put multiple backends in a single unix process, can be a pain to get working on a multi-cpu system unless the OS can handle threads across multiple cpu processes. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026