So what's the blurb about the scheduler. Well, basically the server has different parts which run in parallel and the way the processing power is distributed between them changes the way the server performs under high load. If other processes run on the same server it will also influence how much cpu time dpfTVS gets compared to them. A setting of 2 for the scheduler will therefore shutdown all other services in a high load situation, so handle that carefully. It's not very useful to change the default settings. Most things are covered with the last optimisations I've made in built 2.0.890. However, if you use the computer mainly as web-server you can get a bit better response times with a high setting here, but normally just changing the nice value to -20 should be enough to guaranty good performance.
- main_sched
sets the scheduler pattern for the connection receiving part. 2 is FIFO, 1 is RR, 0 is OTHER, default 2.
- main_nice
In case main_sched is 0, this value represents the nice value (-20 to 19 with -20 highest priority) with
a default of 0. For the scheduler setting of 1 or 2 this is equal to the priority (1-99, with 99 max) of
the program, default is 1.
- cgi_sched
sets the scheduler for the cgi script itself, values other than 0,1,2 will leave the current pattern unchanged, default is 0
- cgi_nice
The same as main_nice, just for the cgi part
|