Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id DF2F11337B3E for ; Fri, 4 Feb 2011 07:33:59 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 66757-07 for ; Fri, 4 Feb 2011 11:33:53 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 92AA21337B2F for ; Fri, 4 Feb 2011 07:33:51 -0400 (AST) Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MZysF-1PRjfN06Pf-00LpAS; Fri, 04 Feb 2011 12:33:50 +0100 Message-ID: <4D4BE41C.5020100@2ndquadrant.com> Date: Fri, 04 Feb 2011 06:33:48 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Andy Colson CC: Scott Marlowe , gnuoytr@rcn.com, pgsql-performance@postgresql.org Subject: Re: getting the most of out multi-core systems for repeated complex SELECT statements References: <20110203105704.BAX82905@ms14.lnh.mail.rcn.net> <4D4B32B9.1020904@2ndquadrant.com> <4D4B70B1.2080809@squeakycode.net> <4D4B79D8.9040402@2ndquadrant.com> <4D4B7E64.4030203@squeakycode.net> In-Reply-To: <4D4B7E64.4030203@squeakycode.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:bCxYzIAwNwOsAE6DMuo2M8STU5JAakXSIPB66LWaD4F dxyaURPZI0cLYdfdGmQT+UaeaH603tHOKuZWoGxAzFANEWPm8l BjyYb6ENepxoyXgg7n/ia7KfVMZSCb5cU88Tseit5YZj9Wkike 9TVidLyHEnhdkrM2+a9IFmrpuciwNUiMHGVU+EV2roJwBgvg7d zzkW1zYmf/f/cR8eOizPejArj710JXhIAVHpDWQWdM= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201102/177 X-Sequence-Number: 42315 Andy Colson wrote: > Yes, I agree... for today. If you gaze into 5 years... double the > core count (but not the speed), double the IO rate. What do you see? Four more versions of PostgreSQL addressing problems people are having right now. When we reach the point where parallel query is the only way around the actual bottlenecks in the software people are running into, someone will finish parallel query. I am not a fan of speculative development in advance of real demand for it. There are multiple much more serious bottlenecks impacting scalability in PostgreSQL that need to be addressed before this one is #1 on the development priority list to me. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books