X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 37DE2535D7 for ; Fri, 22 Apr 2005 17:54:01 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64641-07 for ; Fri, 22 Apr 2005 20:53:51 +0000 (GMT) Received: from priv-edtnes56.telusplanet.net (outbound01.telus.net [199.185.220.220]) by svr1.postgresql.org (Postfix) with ESMTP id 8F51C5323A for ; Fri, 22 Apr 2005 17:53:49 -0300 (ADT) Received: from localhost ([199.185.220.240]) by priv-edtnes56.telusplanet.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050422205350.GVXB24451.priv-edtnes56.telusplanet.net@localhost>; Fri, 22 Apr 2005 14:53:50 -0600 Received: from 209.17.183.249 ( [209.17.183.249]) as user a3a18850@192.168.200.1 by webmail.telus.net with HTTP; Fri, 22 Apr 2005 13:53:50 -0700 Message-ID: <1114203230.4269645e44160@webmail.telus.net> Date: Fri, 22 Apr 2005 13:53:50 -0700 From: Mischa Sandberg To: Alvaro Herrera Cc: Joel Fradkin , 'Andreas Pflug' , 'Dave Page' , pgsql-performance@postgresql.org, ac@wazagua.com, "Joshua D. Drake" , wheyliger@wazagua.com, 'Steve Hatt' Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon References: <4268C833.8080302@pse-consulting.de> <000401c54763$dd684620$797ba8c0@jfradkin> <20050422183054.GB14419@dcc.uchile.cl> In-Reply-To: <20050422183054.GB14419@dcc.uchile.cl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1-cvs X-Originating-IP: 209.17.183.249 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.082 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_POST, FORGED_RCVD_HELO X-Spam-Level: * X-Archive-Number: 200504/624 X-Sequence-Number: 12021 Quoting Alvaro Herrera : > One further question is: is this really a meaningful test? I mean, in > production are you going to query 300000 rows regularly? And is the > system always going to be used by only one user? I guess the question > is if this big select is representative of the load you expect in > production. While there may be some far-out queries that nobody would try, you might be surprised what becomes the norm for queries, as soon as the engine feasibly supports them. SQL is used for warehouse and olap apps, as a data queue, and as the co-ordinator or bridge for (non-SQL) replication apps. In all of these, you see large updates, large result sets and volatile tables ("large" to me means over 20% of a table and over 1M rows). To answer your specific question: yes, every 30 mins, in a data redistribution app that makes a 1M-row query, and writes ~1000 individual update files, of overlapping sets of rows. It's the kind of operation SQL doesn't do well, so you have to rely on one big query to get the data out. My 2c -- "Dreams come true, not free." -- S.Sondheim, ITW