Re: [HACKERS] Help me develop new commit_delay advice

2012-08-02 Thread Peter Geoghegan
On 29 July 2012 16:39, Peter Geoghegan wrote: > Many of you will be aware that the behaviour of commit_delay was > recently changed. Now, the delay only occurs within the group commit > leader backend, and not within each and every backend committing a > transaction: I've moved this to the pgsql-

Re: [HACKERS] Help me develop new commit_delay advice

2012-08-02 Thread Josh Berkus
Peter, For some reason I didn't receive the beginning of this thread. Can you resend it to me, or (better) post it to the pgsql-performance mailing list? I have a linux system where I can test both on regular disk and on SSD. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sen

Re: [HACKERS] Help me develop new commit_delay advice

2012-08-02 Thread Amit Kapila
> From: Peter Geoghegan [mailto:pe...@2ndquadrant.com] > Sent: Wednesday, August 01, 2012 8:49 PM On 1 August 2012 15:14, Amit Kapila wrote: >> I shall look into this aspect also(setting commit_delay based on raw sync). >> You also suggest if you want to run the test with different configuration

Re: [HACKERS] Help me develop new commit_delay advice

2012-08-01 Thread Peter Geoghegan
On 1 August 2012 15:14, Amit Kapila wrote: > I shall look into this aspect also(setting commit_delay based on raw sync). > You also suggest if you want to run the test with different configuration. Well, I was specifically interested in testing if half of raw sync time was a widely useful setting

Re: [HACKERS] Help me develop new commit_delay advice

2012-08-01 Thread Amit Kapila
> From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Peter Geoghegan > Sent: Sunday, July 29, 2012 9:09 PM > I made what may turn out to be a useful observation during the > development of the patch, which was that for both the tpc-b.sql and > insert