X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 54F679DC833 for ; Sun, 29 Jan 2006 20:32:18 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 35249-08 for ; Sun, 29 Jan 2006 20:32:21 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by postgresql.org (Postfix) with ESMTP id 15C1C9DC82E for ; Sun, 29 Jan 2006 20:32:15 -0400 (AST) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail1.panix.com (Postfix) with ESMTP id 1FC0D588A0; Sun, 29 Jan 2006 19:32:18 -0500 (EST) Received: (from adler@localhost) by panix2.panix.com (8.11.6p3/8.8.8/PanixN1.1) id k0U0WIp17092; Sun, 29 Jan 2006 19:32:18 -0500 (EST) Date: Sun, 29 Jan 2006 19:32:15 -0500 From: Michael Adler To: Mike Biamonte Cc: pgsql-performance@postgresql.org Subject: Re: Huge Data sets, simple queries Message-ID: <20060130003215.GA20269@pobox.com> References: <007101c623a9$82207c10$0200a8c0@videobox> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <007101c623a9$82207c10$0200a8c0@videobox> X-PGP-Key-ID: 0xFA0F8E88 X-PGP-Key-Fingerprint: B40D 7C75 C44A 443D 8216 29B8 4B82 2C04 FA0F 8E88 X-PGP-Key-URL: User-Agent: Mutt/1.5.10i X-Hashcash: 1:20:060130:mike@dbeat.com::kKJRtZlcudE+h3ZR:0004MUH X-Hashcash: 1:20:060130:pgsql-performance@postgresql.org::QF46YqlT5i0d1bj1:00000 00000000000000000000000053UM X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.096 required=5 tests=[AWL=0.096] X-Spam-Score: 0.096 X-Spam-Level: X-Archive-Number: 200601/468 X-Sequence-Number: 16946 On Fri, Jan 27, 2006 at 08:23:55PM -0500, Mike Biamonte wrote: > This query took 18 hours on PG 8.1 on a Dual Xeon, RHEL3, (2.4 > Kernel) with RAID-10 (15K drives) and 12 GB Ram. I was expecting it > to take about 4 hours - based on some experience with a similar > dataset on a different machine (RH9, PG7.3 Dual Xeon, 4GB RAM, > Raid-5 10K drives) > > It's difficult to just "try" various ideas because each attempt > takes a full day to test. Real experience is needed here! It seems like you are changing multiple variables at the same time. I think you need to first compare the query plans with EXPLAIN SELECT to see if they are significantly different. Your upgrade from 7.3 to 8.1 may have resulted in a less optimal plan. Second, you should monitor your IO performance during the query execution and test it independent of postgres. Then compare the stats between the two systems. As a side note, if you have many disks and you are concerned about bottlenecks on read operations, RAID 5 may perform better than RAID 10. -Mike