Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id DB8B7475D22 for ; Mon, 20 Jan 2003 02:44:08 -0500 (EST) Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by postgresql.org (Postfix) with ESMTP id 0CC2D475AE6 for ; Mon, 20 Jan 2003 02:44:07 -0500 (EST) Received: (from root@localhost) by www.pspl.co.in (8.11.6/8.11.6) id h0K7i6v06628 for ; Mon, 20 Jan 2003 13:14:06 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) by www.pspl.co.in (8.11.6/8.11.0) with ESMTP id h0K7i6J06623 for ; Mon, 20 Jan 2003 13:14:06 +0530 From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Date: Mon, 20 Jan 2003 13:14:27 +0530 MIME-Version: 1.0 Subject: Re: 7.3.1 New install, large queries are slow Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3E2BF633.14532.D772D99@localhost> References: <3E2BE5DD.30158.D375D9A@localhost> In-reply-to: <27220.1043046883@sss.pgh.pa.us> X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/202 X-Sequence-Number: 849 On 20 Jan 2003 at 2:14, Tom Lane wrote: > "Shridhar Daithankar" writes: > > Assuming that one knows what he/she is doing, would it help in such cases i.e. > > the linear search thing, to bump up page size to day 16K/32K? > > You mean increase page size and decrease the number of buffers > proportionately? It'd save on buffer-management overhead, but > I wouldn't assume there'd be an overall performance gain. The > system would have to do more I/O per page read or written; which > might be a wash for sequential scans, but I bet it would hurt for > random access. Right. But it has its own applications. If I am saving huge data blocks like say gene stuff, I might be better off living with a relatively bigger page fragmentation. > > and that is also the only way to make postgresql use more than couple of gigs > > of RAM, isn't it? > > It seems quite unrelated. The size of our shared memory segment is > limited by INT_MAX --- chopping it up differently won't change that. Well, if my page size is doubled, I can get double amount of shared buffers. That was the logic nothing else. > In any case, I think worrying because you can't push shared buffers > above two gigs is completely wrongheaded, for the reasons already > discussed in this thread. The notion that Postgres can't use more > than two gig because its shared memory is limited to that is > *definitely* wrongheaded. We can exploit however much memory your > kernel can manage for kernel disk cache. Well, I agree completely. However there are folks and situation which demands things because they can be done. This is just to check out the absolute limit what it can manage. Bye Shridhar -- Bagdikian's Observation: Trying to be a first-rate reporter on the average American newspaper is like trying to play Bach's "St. Matthew Passion" on a ukelele.