Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 87B019FA66A for ; Mon, 23 Jul 2007 11:13:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 14525-03 for ; Mon, 23 Jul 2007 11:12:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 5F4599FB340 for ; Mon, 23 Jul 2007 11:12:07 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6NEBfp3023849; Mon, 23 Jul 2007 10:11:42 -0400 (EDT) To: "Simon Riggs" cc: "Jignesh K. Shah" , "Josh Berkus" , pgsql-performance@postgresql.org, "Alvaro Herrera" Subject: Re: User concurrency thresholding: where do I look? In-reply-to: <1185180668.4284.149.camel@ebony.site> References: <200707190828.59088.josh@agliodbs.com> <200707191819.13899.josh@agliodbs.com> <15685.1184895926@sss.pgh.pa.us> <200707192138.39679.josh@agliodbs.com> <46A0FA31.2080208@sun.com> <12002.1184955831@sss.pgh.pa.us> <46A1055F.9010304@sun.com> <12445.1184958793@sss.pgh.pa.us> <46A11116.5030905@sun.com> <14909.1184962561@sss.pgh.pa.us> <46A1205B.8010205@sun.com> <15343.1184965054@sss.pgh.pa.us> <1185180668.4284.149.camel@ebony.site> Comments: In-reply-to "Simon Riggs" message dated "Mon, 23 Jul 2007 09:51:08 +0100" Date: Mon, 23 Jul 2007 10:11:41 -0400 Message-ID: <23848.1185199901@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/289 X-Sequence-Number: 25973 "Simon Riggs" writes: > EState is about 8300 bytes, What? (gdb) p sizeof(EState) $1 = 112 This is on a 32-bit machine, but even on 64-bit it wouldn't be more than double that. > Would it be worth a special case in the palloc system to avoid having to > repeatedly issue external memory allocation calls? The appropriate hack would be to change the AllocSetContextCreate initial-size parameter for the containing context. But I really have no idea what you're on about. regards, tom lane