Re: CommitDelay performance improvement

> When thinking about tuning N, I like to consider what are the interesting
> possible values for N:
>
> 0: Ignore any other potential committers.
> 1: The minimum possible responsiveness to other committers.
> 5: Tom's guess for what might be a good choice.
> 10: Harry's guess.
> ~0: Always delay.
>
> I would rather release with N=1 than with 0, because it actually responds
> to conditions. What N might best be, >1, probably varies on a lot of
> hard-to-guess parameters.
>
> It seems to me that comparing various choices (and other, more interesting,
> algorithms) to the N=1 case would be more productive than comparing them
> to the N=0 case, so releasing at N=1 would yield better statistics for
> actually tuning in 7.2.

We don't release code becuase it has better tuning oportunities for
later releases. What we can do is give people parameters where the
default is safe, and they can play and report to us.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026