06-21-2011
That doesn't tell us much of the problem.
98% would be just fine depending on your CPU configuration.
On the other hand having all application jobs running as root is usually a bad idea.
It would also be helpful to know what are those jobs actually doing (lenghty backups, data processing, system monitoring, simple scripts?)
Those jobs could pretty much be the cause of the slowness as well as they could also be irrelevant to the issue.
Please provide more details of your system, jobs, memory, CPU, vmstat, etc.
EDIT: Duplicated post.
10 More Discussions You Might Find Interesting
1. Solaris
Good morning,
I need some help figuring out what's eating up my cpu. My application can't get enough cpu to do its job. this is a sunfire V440 2CPU's at 1/593 GHZ with 8GB of memory. In the morning hours the box is at less than 3%. I can't figure out what else is using the CPU. We use foglight and... (2 Replies)
Discussion started by: bbouhaik
2 Replies
2. AIX
Hi am facing high cpu utilization on my sybase server.
I have P550
Number Of Processors: 4
Processor Clock Speed: 1656 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 65-D837E
Memory Size: 7840 MB
in topas it shows
Name PID CPU% PgSp Owner
dataserv 565264 ... (1 Reply)
Discussion started by: vjm
1 Replies
3. Shell Programming and Scripting
Hi All,
i have a script that finds the file with .txt .zip .Z .gzip that are 3 days old in directory /abc/def and removes them
find /abc/def -name '0*.txt' -mtime +6 -exec rm {} \;
find /abc/def -name '0*.zip' -mtime +6 -exec rm {} \;
find /abc/def -name '0*.gzip' -mtime +6... (3 Replies)
Discussion started by: mad_man12
3 Replies
4. Shell Programming and Scripting
There is a script which processes the incoming files from a particular directory and sleeps if it doesnt find any. Currently, i have been told that eventhough there are no files to process, the CPU utilization is very high. An independent evaluation by advisory specialist has found this script does... (2 Replies)
Discussion started by: nandu
2 Replies
5. Solaris
Hi,
I am working on a solaris app processor and the vsh goes high from time to time. I have executed various ps commands and switches and have found that it looks like the rlogind daemon is terminating vsh and not cleaning up after itself. There are also something like 10 zombies hanging around... (2 Replies)
Discussion started by: troystevens
2 Replies
6. UNIX for Advanced & Expert Users
good morning.
just wanted to ask if there's a way to check what causes the high cpu utilization of a server for the past 2 months? My jffnms report resulted to high utilization for a specific server last month. is there a way to check via a command line?
thanks (9 Replies)
Discussion started by: lhareigh890
9 Replies
7. Shell Programming and Scripting
Hello all,
I am very new to unix and trying to solve this problem.
I have cluster of 3 nodes. when I run TOP command on each server, I see a two GZIP processess with very high CPU utilization even,if I don't go backups or unzipping.
Can somebody tell me what is the problem, I don't want... (1 Reply)
Discussion started by: nnani
1 Replies
8. UNIX for Advanced & Expert Users
Hi,
i am observing few processes taking high CPU and when i got some more detials about them it looks like this
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9452 xmp 25 0 16736 1224 860 R 100.0 0.0 903:54.18 ffmpeg -i -
9777 xmp 25 0 16736 1224 ... (1 Reply)
Discussion started by: Siddheshk
1 Replies
9. Red Hat
Hi Experts,
I need to understand few basic things regarding top command result from one of the node i have collected:
Cpu0 : 4.6%us, 2.0%sy, 0.0%ni, 91.4%id, 1.3%wa, 0.3%hi, 0.3%si, 0.0%st
Cpu1 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : ... (5 Replies)
Discussion started by: mackjack87
5 Replies
10. Red Hat
Hi,
Please suggest how to troubleshoot, kswapd is utilizing high cpu?
also wanted to know which parameters are important and needs to be added with sar command for monitoring the performance of Linux (Oracle 5.8 -64 bit
Please guide me.
I am facing the issue where server is getting... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
LEARN ABOUT XFREE86
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)