X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 113EDD1D8F3 for ; Tue, 17 Feb 2004 10:36:42 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 79481-09 for ; Tue, 17 Feb 2004 06:36:40 -0400 (AST) Received: from expasy-ng.isb-sib.ch (expasy-f.unige.ch [192.33.215.142]) by svr1.postgresql.org (Postfix) with ESMTP id DFC06D1BB5E for ; Tue, 17 Feb 2004 06:36:36 -0400 (AST) Received: from caliente (router.isb-sib.ch [192.33.215.254]) (authenticated bits=0) by expasy-ng.isb-sib.ch (8.12.10/8.12.8) with ESMTP id i1HAaaYn000554 for ; Tue, 17 Feb 2004 11:36:37 +0100 Message-ID: <00bf01c3f541$ead47f60$c300000a@caliente> From: "Eric Jain" To: "pgsql-performance" References: <4cbacd4cb3c2.4cb3c24cbacd@jhmimail.jhmi.edu> <87u14q6b4c.fsf@mailbox.samurai.com> Subject: Re: very large db performance question Date: Tue, 17 Feb 2004 11:36:35 +0100 Organization: Swiss Institute of Bioinformatics 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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-sib-MailScanner-Information: Please contact the ISP for more information X-sib-MailScanner: Found to be clean X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/178 X-Sequence-Number: 5702 > IMHO the size of the DB is less relevant than the query workload. For > example, if you're storying 100GB of data but only doing a single > index scan on it every 10 seconds, any modern machine with enough HD > space should be fine. I agree that the workload is likely to be the main issue in most situations. However, if your queries involve lots of counting and aggregating, your databases contains several gigabytes of data, and you are using common hardware, be prepared to wait anywhere from minutes to hours, even if you are the only user.