Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VF5Mi-00072l-9n for pgsql-performance@arkaria.postgresql.org; Thu, 29 Aug 2013 16:46:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VF5Mh-0002jS-Kr for pgsql-performance@arkaria.postgresql.org; Thu, 29 Aug 2013 16:46:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VF5Mg-0002jM-PI for pgsql-performance@postgresql.org; Thu, 29 Aug 2013 16:46:34 +0000 Received: from lists.commandprompt.com ([69.168.55.30]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VF5Mc-00087P-02 for pgsql-performance@postgresql.org; Thu, 29 Aug 2013 16:46:33 +0000 Received: from [192.168.1.5] (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id C1A812B3; Thu, 29 Aug 2013 09:46:27 -0700 (PDT) Received: from [192.168.1.5] ([75.142.30.85] helo=[192.168.1.5]) by assp.commandprompt.com with ESMTPS(AES256-SHA) (2.1.1); 29 Aug 2013 09:46:27 -0700 Message-ID: <521F7ACE.5040708@commandprompt.com> Date: Thu, 29 Aug 2013 09:46:06 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: bsreejithin CC: pgsql-performance@postgresql.org Subject: Re: How clustering for scale out works in PostgreSQL References: <1377778443804-5768917.post@n5.nabble.com> <521F61B9.1000709@archonet.com> <521F63DD.3050301@commandprompt.com> <1377792804612-5768951.post@n5.nabble.com> <1377794535276-5768957.post@n5.nabble.com> In-Reply-To: <1377794535276-5768957.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Assp-Version: 2.1.1(11364) on assp.commandprompt.com X-Assp-Client-SSL: yes X-Assp-ID: assp.commandprompt.com m1-94787-13139 X-Assp-Envelope-From: jd@commandprompt.com X-Assp-Intended-For: bsreejithin@gmail.com X-Assp-Original-Subject: Re: [PERFORM] How clustering for scale out works in PostgreSQL X-Pg-Spam-Score: -4.4 (----) 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 On 08/29/2013 09:42 AM, bsreejithin wrote: > > The performance test that was conducted was for 1 Hour. > > There are 6 transactions. 2 DB inserts and 4 SELECTs. > Every 2 minutes there will be 4 SELECTs. And every 3 minutes there will be 2 > DB inserts. This shouldn't be a problem with proper hardware and a connection pooler. The concern isn't the 1000 sessions, it is the creating and destroying in rapid succession of 1000 connections. A connection pooler will resolve that issue. Sincerely, JD -- Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579 PostgreSQL Support, Training, Professional Services and Development High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc For my dreams of your image that blossoms a rose in the deeps of my heart. - W.B. Yeats -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance