On Mon, 2007-04-02 at 16:14 -0700, Jeff Davis wrote:
> The results are very positive and quite conclusive.
Can we show some summary results?
I'm happy that the scans stay together all the way around, even handling
the max-> 0 blockid transition well. So definite winner for me.
> However, the "sync_seqscan_offset" aspect of my patch, which attempts to
> use pages that were cached before the scan began, did not show a lot of
> promise. That aspect of my patch may end up being cut.
Yes, please remove :-)
> The primary aspect of my patch, the Synchronized Scanning, performed
> great though. Even the CFQ scheduler, that does not appear to properly
> read ahead, performed substantially better than plain 8.2.3. And even
> better, Simon's patch didn't seem to hurt Synchronized Scans at all.
> Out of the 36 runs I did, a couple appear anomalous. I will retest those
Which ones were they?
> Note: I posted the versions of the patches that I used for the tests on
> the page above. The version of Simon's patch that I used did not apply
> cleanly to 8.2.3, but the only problem appeared to be in copy.c, so I
> went ahead with the tests. If this somehow compromised the patch, then
> let me know.
[It was never designed to apply cleanly to 8.2.3, as we might guess]
That was v2, the current v3 should be OK because I removed the
experimental COPY interaction. That will not have affected the tests.
I would like to see some tests with different queries that have varying
I/O and CPU requirements to see if they stay together too. That won't
block the patch, but it will help everybody understand what the range of
real world applicability there is in this. I'd guess this can benefit us
sufficiently frequently in most cases that its worth it.
In response to
pgsql-hackers by date
|Next:||From: Hiroshi Saito||Date: 2007-04-03 09:06:16|
|Subject: PthreadGC2 of MinGW is not linked.|
|Previous:||From: Marko Kreen||Date: 2007-04-03 08:56:16|
|Subject: Re: PL/Python warnings in CVS HEAD|