--- In Firebird-Architect@yahoogroups.com, Alex Peshkov <pes@...> wrote:

>
> hanszorn2000:
> > Alex,
> >
> > --- In Firebird-Architect@yahoogroups.com, Alex Peshkov <pes@> wrote:
> >> # The wait time, in milli-seconds (ms), before the priority of:
> >> # - an active thread is reduced to 'Low', or
> >> # - an inactive thread is increased to 'High'
> >> #
> >
> >
> > And the original text from Firebird.conf:
> > # The wait time, in milli-seconds (ms), before the priority of:
> > # - an inactive thread is reduced to 'Low', or
> > # - an active thread is increased to 'High'
> >
> > As this is the inverse of what you write, one of them HAS to be a
> > typo. Or am I missing something?
> >
>
> This text is copyNpaste from current firebird.conf. Where from was

taken

> original I do not remember, it was not me who put it in the list.
>

Unfortunately I am now lost now as to which one is correct and which
is a typo. But what is worse is the fact that, after resetting the
variable to the default, I am still stuck with a system where heavy
queries get all the resources (apparently because their priority is
(set to) high) and light queries must wait all the time. Of course I
can make the value of the parameter smaller, but would that help?
According to the (corrected?) description that would mean that the
priority of active threads would be lowered sooner, so the freshly
active threads can only benefit from their priority boost for a
shorter period of time, resulting in a higher possibility that they
can not be completed in time (i.e. before their priority is lowered).

Hans