Very high nice percentage in top command


 
Thread Tools Search this Thread
Operating Systems BSD Very high nice percentage in top command
# 8  
Old 04-08-2014
The compile jobs are periodic & run by us.
Same job used to complete in ~3 hrs earlier (a week back) which are now taking ~20 hrs.
No configuration change has happened on the system.

Don't see anything else hogging the system.
Hence wondering what's slowing it down.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to use nice command?

Dear Friends, I have a directory when i take du of that directory it takes alot of memory and cpu and I/O, i want to use nice to run my script that have du command slowly so it won't take I/O and cpu, please suggest. (6 Replies)
Discussion started by: learnbash
6 Replies

2. HP-UX

Top cmd showing NICE value 97% -what to tune?

Running 2 VM Guests on an HPUX Integrity Server. One Guest runs great, the other is always at a high NICE value and 0% idle as shown in TOP: What do you think should be tuned to bring down the NICE and increase IDLE %? Thanks in advance -hpuxadmin slow VM GUEST Load averages: 2.56,... (5 Replies)
Discussion started by: hpuxadmin
5 Replies

3. Shell Programming and Scripting

How to see high values on top

Hello folks, I am searching for pattern, after that i want its presenece on top to bottom basis, like cat abcd.txt |grep "123"|awk {'print $3'} |sort|uniq -c it show result like 10 1.1.1.1 1 1.1.1.1 15 1.1.1.1 100 1.1.1.1 but i want to see this like 100 1.1.1.1 15 1.1.1.44 10... (3 Replies)
Discussion started by: learnbash
3 Replies

4. UNIX for Advanced & Expert Users

Is nice command a myth?

Hello, Some guy said to me that using the nice command to decrease the priority of a process is a myth, that the operating system corrects the priorities as the processes need cpu. Is this true? (4 Replies)
Discussion started by: psimoes79
4 Replies

5. AIX

Top command in AIX 4.2 (no topas, no nmon, no top)?

Is there a 'top' command equivalent in AIX 4.2 ? I already checked and I do not see the following ones anywhere: top nmon topas (1 Reply)
Discussion started by: Browser_ice
1 Replies

6. Linux

Help pinpointing high HTTPD CPU usage in TOP

Hi, new here and need some help. Sometimes my site is extremely slow, if when there aren't too many people on, whereas when there are over 300 online members the site may be very fast. We use CentOS, PHP 5.26. The server has 4GB and Plesk usually shows about 2 or 3 GB free. I believe I can see... (4 Replies)
Discussion started by: pspace
4 Replies

7. HP-UX

top and nice

Hi, I have two identical 12 CPU HPUX machines, and I run the same processes on each that load the boxes fully. top on one reports activity under the NICE (19%) and SYS (18%) columns, while top on the other reports 0% NICE and 16% SYS. What would cause NICE to be zero on one machine and not... (5 Replies)
Discussion started by: CBorgia
5 Replies

8. UNIX for Dummies Questions & Answers

The nice command

hello everybody: I have some job running on tru64 system and Im the root, due to limited resources I end up with my job ( vdump) for example taking the lowest share, I researched the nice command on the net, but couldnt get enough info, can I use it to already running process or I only use it... (1 Reply)
Discussion started by: aladdin
1 Replies

9. Programming

nice command and nice() system call

Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
Discussion started by: tejbuch
2 Replies

10. UNIX for Dummies Questions & Answers

[Top output] NICE % high ?

Hi, I've got some CPU bottleneck on a HP-UX 11 server : i didn't understand it until i discover i've got an unusual high percentage of NICE% CPU regarding my DBRMS process (Sybase 12.x). How do i have to understand it and how to resolve it ? Thx. (0 Replies)
Discussion started by: eliador2001
0 Replies
Login or Register to Ask a Question
nice(1) 						      General Commands Manual							   nice(1)

NAME
nice - Runs a command at a different priority SYNOPSIS
Current syntax nice [-n priority] command [argument...] Obsolescent syntax nice [-priority] command [argument...] Note The C shell has a built-in version of the nice command. If you are using the C shell, and want to guarantee that you are using the command described here, you must specify the full path /usr/bin/nice. See the csh(1) reference page for a description of the built-in command. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: nice: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Specifies how the system scheduling priority of the executed utility is adjusted. The priority argument is a positive or negative decimal integer. Positive priority values cause a lower or unchanged system scheduling priority. Negative priority values might require appropriate privileges and cause a higher or unchanged system scheduling priority. Specifies how the system scheduling priority of the executed utility is adjusted. (Obsolescent) OPERANDS
The name of a utility that is to be invoked. Any string to be supplied as an argument to the utility named by the command operand. DESCRIPTION
The nice command lets you run the specified command at a lower priority. The value of priority can range from 1 to 19, with 19 being the lowest priority. The default value of priority is 10. [Tru64 UNIX] If you have superuser authority, you can run commands at a higher priority by specifying priority as a negative number; for example, -10. NOTES
The csh command contains a built-in subcommand named nice. The command and subcommand do not necessarily work the same way. For informa- tion on the subcommand, see the csh command. EXIT STATUS
The nice command returns the following exit values: An error occurred in the nice utility. The specified command was found but could not be invoked. The specified command could not be found. EXAMPLES
To run a low priority command in the background, enter: nice cc -c *.c & This runs the command cc -c *.c at low priority in the background. Your terminal is free so that you can run other commands while cc is running. See the sh command for details about starting background processes with an & (ampersand). To specify a very low prior- ity, enter: nice -n 15 cc -c *.c & This runs cc in the background at a priority that is even lower than the default priority set by nice. To specify a very high pri- ority (ksh and sh only), enter: nice -n -10 wall <<end System shutdown in 2 minutes! end This runs wall at a higher priority than all user processes. Doing this slows down everything else running on the system. If you do not have superuser authority when you run this command, then the wall command runs at the normal priority. The <<end and end arguments define a Here Document, which uses the text entered before the end line as standard input for the com- mand. For more details, see the Inline Input (Here) Documents section on the sh(1) reference page. ENVIRONMENT VARIABLES
The following environment variables affect the execution of nice: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. Determines the search path used to locate the command invoked. SEE ALSO
Commands: csh(1), nohup(1), renice(8) Functions: nice(3), setpriority(2) Standards: standards(5) nice(1)