Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1boVQg-00056i-Nr for pgsql-performance@arkaria.postgresql.org; Mon, 26 Sep 2016 12:54:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1boVQg-0007j1-AL for pgsql-performance@arkaria.postgresql.org; Mon, 26 Sep 2016 12:54:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1boVQe-0007Zx-Kl for pgsql-performance@postgresql.org; Mon, 26 Sep 2016 12:54:40 +0000 Received: from smtp-out-no.shaw.ca ([64.59.134.13]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1boVQb-0008GV-5N for pgsql-performance@postgresql.org; Mon, 26 Sep 2016 12:54:38 +0000 Received: from home.zioup.com ([96.51.153.133]) by shaw.ca with SMTP id oVQWbpPv9FfiXoVQXb3CwX; Mon, 26 Sep 2016 06:54:34 -0600 X-Authority-Analysis: v=2.2 cv=Qb8khYTv c=1 sm=1 tr=0 a=pcwx/iW1S4GNAxS9KzaPFA==:117 a=pcwx/iW1S4GNAxS9KzaPFA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=GW1xBdLrtEIA:10 a=N8iSzGwtAAAA:8 a=F373w0pcBINis5xHbucA:9 a=QEXdDO2ut3YA:10 a=8kBBdpEVvi0A:10 a=YHuoxGDvEISy2GqV2ok9:22 Received: from [192.168.246.243] (epicurus.zioup.net [192.168.246.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by home.zioup.com (Postfix) with ESMTPSA id 29C38A04AC for ; Mon, 26 Sep 2016 06:54:32 -0600 (MDT) Subject: Re: Millions of tables To: pgsql-performance@postgresql.org References: From: Yves Dorfsman Message-ID: Date: Mon, 26 Sep 2016 06:54:31 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfKP4Tw/WJAM41NYxVqMqPI+gu4iPWayD9ux8ievATT72YdVHcK3zGZ0bSOrSv2z+1YR6TtBRq0nEJddblXit1+89+TGHWtR+JU5tqMWZKc8lTkHK5gZN DZnpewCCpgcH/e6MWNDYhcUsDd4SlXTLxFSIUWKgy+oV6wjiXkIh6deACAC259KGNibBXz5q4hTVhg== X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Something that is not talked about at all in this thread is caching. A bunch of memcache servers in front of the DB should be able to help with the 30ms constraint (doesn't have to be memcache, some caching technology). -- http://yves.zioup.com gpg: 4096R/32B0F416 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance