- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: timeslice
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2003 06:50 PM
02-09-2003 06:50 PM
Hi,
I have tuned my kernel parameter timeslice to be 10.
I have had a software vendor come in and do a review of the system and they have recommended that it should be to 20.
Now Ive always tuned the parameter from 1 to 10 and thought I should leave it at that.
The server is a N-Class with 4 x 440Mhz.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2003 07:37 PM
02-09-2003 07:37 PM
Re: timeslice
Setting the timslice value to 20 should not pose a problem. Just remember setting this too low (-1) or a higher value, may cause the process to continue running without checking for signals. Have a look at the information from the kernel parameter page below.
HTH
Michael
==============================================
timeslice
timeslice defines the scheduling-timeslice interval.
Acceptable Values:
Minimum
-1
Maximum
2147483647 (approximately 8 months)
Default
10 (ten 10-msec ticks)
Specify integer value or use integer formula expression. For more information, see Specifying Parameter Values.
Description
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.
No memory allocation relates to this parameter. Some CPU time is spent at each timeslice interval, but this time has not been precisely measured.
Related Parameters
None.
Additional Information
Overview of process parameters
List of process parameters
Browse configurable kernel parameters help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2003 07:52 PM
02-09-2003 07:52 PM
Re: timeslice
Tuning to 20 should not cause any problems.Tuning the parameter to higher values can result in problems.
However,HP does not recommend to tune the parameter from its default values.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2003 08:00 PM
02-09-2003 08:00 PM
Re: timeslice
HP does not recommend to deviate from the default value of 10.
However, you may run into political issues if the recommendation is from the vendor.
So, the best bet is to make it 20 and run load tests and see how the system responds. Put it back to 10 and compare the results with that of 20. If you see no difference, then convey it to the vendor and keep the running kernel. If you see the difference you know what to do.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2003 09:18 AM
02-10-2003 09:18 AM
Solutionyour "batch" processes will love it, but your intercative processes may starve!
Only change "timeslice" in very small increments/decrements (like 1 or 2!), then check for your results - and don't change aynthing else at the same time as that would certainly spoil your measurement!
FWIW,
Wodisch
PS:In three words: try "12" first!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 02:55 PM
02-11-2003 02:55 PM
Re: timeslice
Does this mean that all heavy batch jobs will suck up CPU and the guys who are just keying data and doing small update will be affected?
Im going to adjust to 12 and suck and see.
What would be a good measure to see any improvement? less context switching?
thanks for your help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 03:04 PM
02-11-2003 03:04 PM
Re: timeslice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 03:14 PM
02-11-2003 03:14 PM
Re: timeslice
I am assuming that the software vendor is the one who supplied you with the software/application.
If your vendor recommended a setting, then there could be a reason because he knows how his software works. Probably the work it does may need 20 ticks.
Use "it depends" concept. Probably his software may benefit from minimum context switching. Do testing with a variety of settings and go with your findings.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2003 03:17 PM
02-11-2003 03:17 PM
Re: timeslice
Hate to quibble here & no disrespect to Stephen intended, but it seems to me that because it's the max ticks value that any equal priority process can get AND because there's no guarantee your process is next in the priority queue, wouldn't it make more sense to say:
"It's the *minimum* number of ticks you ain't gonna get."
Maximum would be good IF there were only 2 processes - both with the same priority & they both wanted to remain processing beyond 10 ticks....
And for that matter 10 as a minimum may not be accurate either IF the preceeding process(es) only needed 1 or 2 ticks.....
Hmmmmm......intriguing to say the least, and I do like the analogy........
My $0.02,
Jeff