Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 35DF24DA6A7 for ; Thu, 10 May 2012 05:36:18 -0300 (ADT) Received: from rs133.luxsci.com ([72.32.115.26]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SSOr6-0006WP-17 for pgsql-admin@postgresql.org; Thu, 10 May 2012 08:36:17 +0000 Received: from GNANAM (NSG-Static-236.156.72.182.airtel.in [182.72.156.236] (may be forged)) (authenticated bits=0) by rs133.luxsci.com (8.13.8/8.13.8) with ESMTP id q4A8YQB7014360; Thu, 10 May 2012 03:35:55 -0500 Reply-To: From: "Gnanakumar" To: "'Kevin Grittner'" , References: <00da01cd2ce7$35d17780$a1746680$@com> <00e101cd2cfc$b6140b00$223c2100$@com> <4FA8E99B0200002500047A16@gw.wicourts.gov> <001f01cd2dd0$4187f8d0$c497ea70$@com> <4FAA3F740200002500047A73@gw.wicourts.gov> <005401cd2e7c$19fb1480$4df13d80$@com> In-Reply-To: <005401cd2e7c$19fb1480$4df13d80$@com> Subject: Re: Advice/guideline on increasing shared_buffers and kernel parameters Date: Thu, 10 May 2012 14:02:56 +0530 Organization: Zoniac Software Private Limited Message-ID: <005e01cd2e87$81d58850$858098f0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac0t9AhpRIdW8tI1RWyjkt19DvrTTwAhYu/gAAMjB6A= Content-Language: en-us X-Lux-Comment: Message q4A8YQB7014360 sent by user #22393 X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201205/54 X-Sequence-Number: 39543 > A formula which has held up pretty well across a lot of benchmarks > for years is that for optimal throughput the number of active > connections should be somewhere near > ((core_count * 2) + effective_spindle_count). Our entire Production application stack is setup in Amazon EC2 cloud environment, that includes database server also. So, in that case, how do I find out "effective_spindle_count"? I know "core_count" can be determined from Amazon EC2 instance type. Per Amazon EC2, EBS volumes are reportedly a shared resource.