topic Re: "timeslice" kernel setting in Operating System - HP-UX

"timeslice" kernel setting

Tony Willis_1 — Tue, 24 Oct 2000 16:56:18 GMT

I have read several different responses to the question concerning "timeslice"
numerical value. By "SERVER TEMPLATE" default it is set to "1".

The older system (K580) that I am replacing with a dual 550MHZ N4000
has it set to "10". Is there a set answer? I am running Oracle 8.05 .

Re: "timeslice" kernel setting

James R. Ferguson — Tue, 24 Oct 2000 16:59:38 GMT

Tony:

The timeslice interval is the amount of time one process is allowed to run before the CPU is given to the next process at the same priority. The value of timeslice is specified in units of (10 millisecond) clock ticks. There are two special values:

0 => Use the system default value (currently ten 10-msec ticks, or 100 milliseconds).

-1 => Disable round-robin scheduling completely.

Timeslice imposes a time limit which, when it expires, forces a process to check for pending signals. This guarantees that any processes that do not make system calls can be terminated (such as a runaway process in an infinite loop). Setting timeslice to a very large value, or to minus 1, allows such processes to continue operating without checking for signals, thus causing system performance bottlenecks or system lock-up.

Use the default value for timeslice unless a different value is required by system applications having specific real-time needs.

...JRF...

Re: "timeslice" kernel setting

Alan Riggs — Tue, 24 Oct 2000 17:02:18 GMT

From http://docs.hp.com//hpux/onlinedocs/os/KCparam.TimeSlice.html

The timeslice interval is the amount of time one process is allowed to run before the CPU is given to the next process at the same priority. The value of timeslice is specified in units of (10 millisecond) clock ticks. There are two special values:

0 Use the system default value (currently ten 10-msec ticks, or 100 milliseconds).

-1 Disable round-robin scheduling completely.

Impact on System
timeslice imposes a time limit which, when it expires, forces a process to check for pending signals. This guarantees that any processes that do not make system calls can be terminated (such as a runaway process in an infinite loop). Setting timeslice to a very large value, or to minus 1, allows such processes to continue operating without checking for signals, thus causing system performance bottlenecks or system lock-up.

Use the default value for timeslice unless a different value is required by system applications having specific real-time needs.

Re: "timeslice" kernel setting

Alan Riggs — Tue, 24 Oct 2000 17:03:30 GMT

Damn -- that's why James is royalty. He has lightning fast C&P reflexes.

Re: "timeslice" kernel setting

James R. Ferguson — Tue, 24 Oct 2000 17:06:56 GMT

Alan (Hello!):

Ah shucks! I just got lucky. Great minds run in the same tracks. Great to see you back regularly!

Warm regards, Jim.

...JRF...