Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E3DDB633223 for ; Fri, 11 Jun 2010 03:25:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 90630-09 for ; Fri, 11 Jun 2010 06:25:49 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from web39702.mail.mud.yahoo.com (web39702.mail.mud.yahoo.com [209.191.106.48]) by mail.postgresql.org (Postfix) with SMTP id 0CE18632A30 for ; Fri, 11 Jun 2010 03:25:48 -0300 (ADT) Received: (qmail 76275 invoked by uid 60001); 11 Jun 2010 06:25:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1276237547; bh=IOCvaKgx0RjF46bwNpjxDvklZIJ6MvLoYaxF2ED62Ok=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rDDfJ/XZPd4Hf/wyMoXxF5m6g45yf4sQHhv8ibjmq/1s4ZT+55+qUV6Mdheq8ktQadZLtYUvYjRvQaRkcYNgLbL5dJlyfSXXqFsxFjzC7L6fdCRGxGMdvh1JDBD/xe4Q2J5dPP3k+EKXmXe5cnytN03OB8w2ed15ILbzTKGZX04= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Mbk9Zox89Kt1Y29rZpeTc6FT8O13+sQQymX8U+k/yFGr8BQjsMsh5LZFDvl3FHoZUT9lrPHN0sQ9fdsSTBTkelh4QjhU1NyJzqwoRR8tAYd4QD+yAT9t7vP8d9qMy5/zlMWNbB3KBpE6Qj2k9TJ988jyjthnO7ikRGn6AqvnhbM=; Message-ID: <584872.74177.qm@web39702.mail.mud.yahoo.com> X-YMail-OSG: C4UguoEVM1kPujiyUsj55Q0v7sqSVlPcSIRAM.86OnOPSs_ 8dOcBLBEakdH4NhqUM0Gu0yxlQ8SIDUgQX56dePGoWNgVG4vF5uBC_GNpPAd cG5Zpu0JAnwm6LiIgvBFkTsXjfssgmlKjBjvg1zoX3BVuH8wtr8ShW.EEmZo KP4eBEE256WBkDyoshE0GaZQdAzD6n.vFI1pDp9_HR.tjhI7UzzFjw10jXPi GuYLvybnkqzcCLtNWZbNbA4vWvRXTOpnzK108kzz_FKgzffz4mKiWlyzaylb ZNKaqKO5UBGYS8iEz0nMZFp69SlLZch6Su_KZpaM96a5wIYf9DElHMmqnYJ5 nMBxzE9MjbUfrc2BqyM8POMqwJu.M8l720LQ- Received: from [69.76.130.83] by web39702.mail.mud.yahoo.com via HTTP; Thu, 10 Jun 2010 23:25:47 PDT X-Mailer: YahooMailClassic/11.1.3 YahooMailWebService/0.8.103.269680 Date: Thu, 10 Jun 2010 23:25:47 -0700 (PDT) From: Bob Lunney Subject: Re: requested shared memory size overflows size_t To: Tom Wilcox Cc: pgsql-performance@postgresql.org In-Reply-To: <4C10FA6C.6060600@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201006/199 X-Sequence-Number: 39055 Tom,=0A=0AFirst off, I wouldn't use a VM if I could help it, however, somet= imes you have to make compromises. With a 16 Gb machine running 64-bit Ubu= ntu and only PostgreSQL, I'd start by allocating 4 Gb to shared_buffers. T= hat should leave more than enough room for the OS and file system cache. T= hen I'd begin testing by measuring response times of representative queries= with significant amounts of data.=0A=0AAlso, what is the disk setup for th= e box? Filesystem? Can WAL files have their own disk? Is the workload OL= TP or OLAP, or a mixture of both? There is more that goes into tuning a PG= server for good performance than simply installing the software, setting a= couple of GUCs and running it.=0A=0ABob=0A=0A--- On Thu, 6/10/10, Tom Wilc= ox wrote:=0A=0A> From: Tom Wilcox =0A> Subject: Re: [PERFORM] requested shared memory size overflows size_t= =0A> To: "Bob Lunney" =0A> Cc: "Robert Haas" , pgsql-performance@postgresql.org=0A> Date: Thursday, June = 10, 2010, 10:45 AM=0A> Thanks guys. I am currently=0A> installing Pg64 onto= a Ubuntu Server 64-bit installation=0A> running as a VM in VirtualBox with= 16GB of RAM accessible.=0A> If what you say is true then what do you sugge= st I do to=0A> configure my new setup to best use the available 16GB (96GB= =0A> and native install eventually if the test goes well) of RAM=0A> on Lin= ux.=0A> =0A> I was considering starting by using Enterprise DBs tuner to=0A= > see if that optimises things to a better quality..=0A> =0A> Tom=0A> =0A> = On 10/06/2010 15:41, Bob Lunney wrote:=0A> > True, plus there are the other= issues of increased=0A> checkpoint times and I/O, bgwriter tuning, etc.=A0= It may=0A> be better to let the OS cache the files and size=0A> shared_buf= fers to a smaller value.=0A> > =0A> > Bob Lunney=0A> > =0A> > --- On Wed, 6= /9/10, Robert Haas=A0=0A> wrote:=0A> > =0A> >=A0 =A0= =0A> >> From: Robert Haas=0A> >> Subject: Re: [PERF= ORM] requested shared memory=0A> size overflows size_t=0A> >> To: "Bob Lunn= ey"=0A> >> Cc: pgsql-performance@postgresql.org,=0A> = "Tom Wilcox"=0A> >> Date: Wednesday, June 9, 2010= , 9:49 PM=0A> >> On Wed, Jun 2, 2010 at 9:26 PM, Bob=0A> >> Lunney=0A> >> wrote:=0A> >>=A0 =A0 =A0 =0A> >>> Your other option, o= f course, is a nice 64-bit=0A> linux=0A> >>>=A0 =A0 =A0 =A0 =0A> >> variant= , which won't have this problem at all.=0A> >> =0A> >> Although, even there= , I think I've heard that=0A> after 10GB=0A> >> you don't get=0A> >> much b= enefit from raising it further.=A0 Not=0A> sure if=0A> >> that's accurate o= r=0A> >> not...=0A> >> =0A> >> -- Robert Haas=0A> >> EnterpriseDB: http://w= ww.enterprisedb.com=0A> >> The Enterprise Postgres Company=0A> >> =0A> >>= =A0 =A0 =A0 =0A> > =0A> > =0A> >=A0 =A0 =0A> =0A> =0A=0A=0A