"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> And we always will have to enable fsync when comparing our
> performance with other DBes.
Of course, but when people say "it's slower than 7.0.3+nofsync"
I think that turning off fsync makes a fairer comparison there.
>> also reduce the WAL commit delay to zero, no? What is the default
> I think so.
>> commit delay now?
> As before 5 * 10^(-6) sec - pretty the same as sleep(0) -:)
> Seems CommitDelay is not very useful parameter now - XLogFlush
> logic and fsync time add some delay.
There was a thread recently about smarter ways to handle shared fsync
of the log --- IIRC, we talked about self-tuning commit delay, releasing
waiting processes as soon as someone else had fsync'd, etc. Looks like
none of those ideas are in the code now. Did you not like any of those
ideas, or just no time to work on it yet?
regards, tom lane
