Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 72B5347630B for ; Fri, 3 Jan 2003 15:47:23 -0500 (EST) Received: from local.iboats.com (local.iboats.com [209.63.105.131]) by postgresql.org (Postfix) with SMTP id 93D1E475E88 for ; Fri, 3 Jan 2003 15:47:22 -0500 (EST) Received: (qmail 11791 invoked by uid 82); 3 Jan 2003 13:47:00 -0700 Received: from nw@codon.com by local.iboats.com by uid 81 with qmail-scanner-1.14 ( Clear:. Processed in 0.026228 secs); 03 Jan 2003 20:47:00 -0000 Received: from unknown (HELO WEASEL) (209.63.105.136) by 0 with SMTP; 3 Jan 2003 13:47:00 -0700 Message-ID: <006601c2b369$a2427ec0$88693fd1@WEASEL> From: "Steve Wolfe" To: References: Subject: Re: Question on hardware & server capacity Date: Fri, 3 Jan 2003 13:49:33 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/25 X-Sequence-Number: 672 > Actually, free memory doesn't mean a whole lot. How much memory is being > used as cache by the kernel? Generally, a gig or so. > Can you distribute your dataset across multiple machines? or is it the > kinda thing that all needs to be in one big machine? 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. steve