Subject | Thread priorities |
---|---|
Author | hanszorn2000 |
Post date | 2006-11-06T16:45:42Z |
(this message was originally posted in Firebird-general. Sorry if it
reaches you twice).
Inspired by the apparent interest in VAX-VMS in this group, I was
thinking of the following.
One of the genial concepts of VAX-VMS is the idea of dynamic
priorities, implemented in such a way that inactive users/ processes
get an increase of priority, whereas active processes are lowered
after some seconds of activity. Why is this genial? Because this is
what gives users the impression of a fast responding system. Processes
that require a little amount of cpu time to complete a users request
will then be processed immediately, while procces that take longer
will have to wait a little more, which won't be noticed as they take
some time anyway.
Within Firebird however this principle seems to be reversed, which
i.m.h.o. is a bad idea. In the Firebird.conf file I read this:
# ----------------------------
# Settings for the thread scheduler (Windows Only)
#
# 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'
So my question is this: hello Firebird guru's, do you have a good
explanation for this, or is this the opening to a nice improvement?
Regards, Hans
reaches you twice).
Inspired by the apparent interest in VAX-VMS in this group, I was
thinking of the following.
One of the genial concepts of VAX-VMS is the idea of dynamic
priorities, implemented in such a way that inactive users/ processes
get an increase of priority, whereas active processes are lowered
after some seconds of activity. Why is this genial? Because this is
what gives users the impression of a fast responding system. Processes
that require a little amount of cpu time to complete a users request
will then be processed immediately, while procces that take longer
will have to wait a little more, which won't be noticed as they take
some time anyway.
Within Firebird however this principle seems to be reversed, which
i.m.h.o. is a bad idea. In the Firebird.conf file I read this:
# ----------------------------
# Settings for the thread scheduler (Windows Only)
#
# 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'
So my question is this: hello Firebird guru's, do you have a good
explanation for this, or is this the opening to a nice improvement?
Regards, Hans