Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> I've been working on the patch to enhance our group commit behavior. The
> patch is a dirty hack at the moment, but I'm settled on the algorithm
> I'm going to use and I know the issues involved.
> The timeout is currently hard-coded at 1 ms.
This is where my bogometer triggered. There's way too many platforms
where 1 msec timeout is a sheer fantasy. If you cannot make it perform
well with a 10-msec timeout then I don't think it's going to be at all
Now I know that newer Linux kernels tend to ship with 1KHz scheduler
tick rate, so there's a useful set of platforms where you could make it
work even so, but I'm not really satisfied with saying "this facility is
only usable if you have a fast kernel tick rate" ...
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Pavan Deolasee||Date: 2007-03-29 16:38:40|
|Subject: Re: CREATE INDEX and HOT - revised design|
|Previous:||From: Teodor Sigaev||Date: 2007-03-29 16:21:38|
|Subject: tsearch_core patch for inclusion|