I noticed when having some trouble with code I was testing that the CPU was becoming exhausted and I would have to reboot. After rebooting a couple times I decided to check for other problems before trying my code again. That's when I noticed that the CPU with the idle process was through the roof:
I wanted to use lsof on the process, but apparently that is not an option with kFreeBSD. I tried using sockstat, but it seemed that no parameters I tried worked. I tried searching online, but all the documentation seemed to be for FreeBSD and not kFreeBSD. The man page didn't seem to be much help either.
Dear All,
Our HPUX 8 GB 8CPU database server is behaving abnormally for the last 4+ weeks. I have generated a sar output and it is here-
11:46:52 %usr %sys %wio %idle
11:46:53 1 1 6 92
11:46:54 0 1 0 99
11:46:55 0 1 0... (3 Replies)
Since yesterday the vmstat command is displaying the cpu idle time at 100%At each time interval. It never changes. Not sure what it means other than it Quit calculating that stat. And I'm curious why. Using sar I can display a correctCpu idle percent, but vmstat does not. Any ideas why or... (2 Replies)
hi,
i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Hi, I checking yesterday's SAR logs for one of our servers and it was showing that utilisation was down to 0% for 10 minutes at 2am. We're unaware of any jobs running at this time so need to find out which process caused this spike.
Is there anything built into SAR (or does anything else exist)... (11 Replies)
I am using Ubuntu 9.04. I want to write a shell script to get the information about cpu idle from top command at the real time when i call it, compare cpu idle with 20 (20%), if cpu idle > 20 exit 1, vice versa exit 0. Anybody can help me to resolve it ?
Thanks alot. (7 Replies)
I need a shell script that will monitor a few conditions and not execute until the these conditions are met. The problem I'm having is that I can not perform a database snapshot (backup) of a sybaseIQ database unless the CPU Status Idle % is above 60% or the snapshot (backup) fails.
If... (2 Replies)
Hi Everybody,
Can anybody explain how CPU idle% is about 50%, but runq-sz more than 1?
sar from Solaris 10:
00:00:05 %usr %sys %wio %idle
17:00:08 27 12 0 61
17:20:05 40 15 0 45
17:40:05 27 12 0 61
18:00:05 23... (2 Replies)
Discussion started by: sant
2 Replies
LEARN ABOUT OSX
dapptrace
dapptrace(1m) USER COMMANDS dapptrace(1m)NAME
dapptrace - trace user and library function usage. Uses DTrace.
SYNOPSIS
dapptrace [-acdeFlhoU] [-u lib] { -p PID | command }
DESCRIPTION
dapptrace prints details on user and library function calls. By default it traces user functions only, options can be used to trace library
activity.
Of particular interest is the elapsed times and on cpu times, which can identify both function calls that are slow to complete, and those
which are consuming CPU cycles.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS -a print all details
-b bufsize
dynamic variable buffer size. Increase this if you notice dynamic variable drop errors. The default is "4m" for 4 megabytes per CPU.
-c print function call counts
-d print relative timestamps, us
-e print elapsed times, us
-F print flow indentation
-l force printing of pid/lwpid per line
-o print on-cpu times, us
-p PID examine this PID
-u lib trace this library instead
-U trace all library and user functions
EXAMPLES
run and examine the "df -h" command,
# dapptrace df -h
examine PID 1871,
# dapptrace -p 1871
print using flow indents,
# dapptrace -Fp 1871
print elapsed and CPU times,
# dapptrace -eop 1871
FIELDS
PID/LWPID
Process ID / Lightweight Process ID
RELATIVE
relative timestamps to the start of the thread, us (microseconds)
ELAPSD elapsed time for this system call, us
CPU on-cpu time for this system call, us
CALL(args)
function call name, with some arguments in hexadecimal
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
dapptrace will run forever until Ctrl-C is hit, or if a command was executed dapptrace will finish when the command ends.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO dappprof(1M), dtrace(1M), apptrace(1)version 1.10 May 14, 2005 dapptrace(1m)