From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: in-transaction insert performance in 7.5devel |
Date: | 2004-06-11 21:30:50 |
Message-ID: | 18742.1086989450@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> Tom Lane wrote:
>> Does it help if you change FlushBuffer to release buffer lock while
>> flushing xlog?
> Putting your change in resulted in about a 15% increase in insert
> performance. There may be some quirky things going on here with NTFS...
> I did an update clean from cvs and I noticed big speedup across the
> board. Right now sync performance is right in line with my
> expectations. In any case, I checked and confirm that there are no
> spurious fsyncs running when they are not supposed to be.
Was that 15% before or after updating from CVS?
The more I think about the looping aspect the less I like it, so I'd
prefer not to pursue making the unlock change for real. But if it's
really a 15% win then maybe we need to...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vitaly Belman | 2004-06-13 03:21:17 | Additional select fields in a GROUP BY |
Previous Message | Merlin Moncure | 2004-06-11 21:04:44 | Re: in-transaction insert performance in 7.5devel |