Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 63EA6476E32 for ; Mon, 6 Jan 2003 14:12:13 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 2F225476DD1 for ; Mon, 6 Jan 2003 14:12:12 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2305182; Mon, 06 Jan 2003 11:12:15 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "Steve Wolfe" , Subject: Re: Question on hardware & server capacity Date: Mon, 6 Jan 2003 11:14:50 -0800 X-Mailer: KMail [version 1.4] References: <006601c2b369$a2427ec0$88693fd1@WEASEL> In-Reply-To: <006601c2b369$a2427ec0$88693fd1@WEASEL> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301061114.50830.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/33 X-Sequence-Number: 680 Steve, > We're splitting the front-end across a number of machines, but all of > the various datasets are sufficiently intertwined that they all have to be > in the same database. I'm going to fiddle around with some of the > available replication options and see if they're robust enough to put them > into production. 2 other suggestions: 1. Both PostgreSQL Inc. and Command Prompt Inc. have some sort of pay-for H= A=20 solution for Postgres. Paying them may end up being cheaper than=20 improvising this yourself. 2. Zapatec Inc. has acheived impressive performance gains by putting the=20 database on a high-speed, HA gigabit NAS server and having a few "client=20 servers" handle incoming queries. You may want to experiment along thes= e=20 lines. --=20 -Josh Berkus Aglio Database Solutions San Francisco