Re: Seq scans roadmap - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Seq scans roadmap
Date
Msg-id 1179249935.24902.114.camel@dogma.v10.wvs
Whole thread Raw
In response to Re: Seq scans roadmap  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Seq scans roadmap
Re: Seq scans roadmap
List pgsql-hackers
On Tue, 2007-05-15 at 10:42 +0100, Heikki Linnakangas wrote:
> Luke Lonergan wrote:
> > 32 buffers = 1MB with 32KB blocksize, which spoils the CPU L2 cache
> > effect.
> > 
> > How about using 256/blocksize?
> 
> Sounds reasonable. We need to check the effect on the synchronized 
> scans, though.
> 

I am a little worried that there will be greater differences in position
as the number of scans increase. If we have only 8 buffers and several
scans progressing, will they all be able to stay within a few buffers of
eachother at any given time?

Also, with 8 buffers, that means each scan must report every 4 pages at
most (and maybe every page), which increases lock contention (the new
design Heikki and I discussed requires a lock every time a backend
reports its position).

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Managing the community information stream
Next
From: Alvaro Herrera
Date:
Subject: Re: Invalid magic number in log file?