Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-22 Thread Mark Cave-Ayland
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane > Sent: 17 February 2005 15:46 > To: Mark Cave-Ayland > Cc: pgsql-patches@postgresql.org > Subject: Re: [PATCHES] WIP: bufmgr rewrite per recent discussions (cut) &

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-17 Thread Tom Lane
"Mark Cave-Ayland" <[EMAIL PROTECTED]> writes: > As I see it, there is not much noticeable performance gain (and maybe even a > small loss)with the padding included. Looks that way. Of course we should never trust a single test case very far, but this suggests that there's not a whole lot of gold

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-17 Thread Mark Cave-Ayland
Hi Tom, Here are the results (tps) from your second patch (LH column is including connection establishments, RH column is excluding connection establishments) using the same test, i.e. pgbench -s 10 -c 10 -t 1000 -d pgbench Shared_buffers 1000

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Tom Lane
"Mark Cave-Ayland" <[EMAIL PROTECTED]> writes: > OK I'm just about finished for the day now. If you email the details of > exactly which tests/parameters you would like me to run, I'll try and run > them tomorrow morning when I have a few spare minutes. I've posted another version of the buffer re

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Mark Kirkwood
Tom Lane wrote: I don't feel this is quite ready to commit, but here it is if anyone would like to try some performance testing. Using "pgbench -s 10" on a single-CPU machine, I find this code a little slower than CVS tip at shared_buffers = 1000, but noticeably faster (~10% speedup) at 1 buff

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Mark Cave-Ayland
> -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 16 February 2005 17:28 > To: Mark Cave-Ayland > Cc: pgsql-patches@postgresql.org > Subject: Re: [PATCHES] WIP: bufmgr rewrite per recent discussions (cut) > What do you mean by "pause&

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Tom Lane
"Mark Cave-Ayland" <[EMAIL PROTECTED]> writes: > Reducing bgwriter_maxpages definitely seems to have helped with the larger > values for shared_buffers. However, during the test I was still seeing large > pauses that occurred at a rate that seemed inversely proportional to the > number of shared bu

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Mark Cave-Ayland
Hi Tom, > -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED] > Sent: 16 February 2005 15:01 > To: Mark Cave-Ayland > Cc: pgsql-patches@postgresql.org > Subject: Re: [PATCHES] WIP: bufmgr rewrite per recent discussions > > > "Mark Cave-Ay

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Tom Lane
"Mark Cave-Ayland" <[EMAIL PROTECTED]> writes: > I compiled and tested your patch on a dual Opteron server with 12GB RAM > running FC3. Here are the results I get with pgbench with a scale-factor of > 10 over an average of 6 runs. Thanks for posting these results. What -c and -t settings were you

Re: [PATCHES] WIP: bufmgr rewrite per recent discussions

2005-02-16 Thread Mark Cave-Ayland
Hi Tom, I compiled and tested your patch on a dual Opteron server with 12GB RAM running FC3. Here are the results I get with pgbench with a scale-factor of 10 over an average of 6 runs. All other postgresql.conf options were left at their default values. CVS tip results --- Shared b