06-05-2016
As the load averages (short to mid time) are all around some 25%, there doesn't seem to be reason for concern. The node is busy, but not too busy, and there's enough headroom, cpu-wise.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi guys,
i am having a dual cpu xeon machine.
i came to know that i can view the performance by giving top command.
but top command shows only the usage of one cpu in percentage
while the process are using more than 100% usage in the list .
can i know separately the usage of cpus.
can you... (5 Replies)
Discussion started by: bijuhpd
5 Replies
2. SCO
Is there a command in SCO Unix that does the same as the top command in HPUX. The command displays the jobs using the most system resources.
Thanks You (0 Replies)
Discussion started by: joestrosser
0 Replies
3. AIX
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
4. Shell Programming and Scripting
Hi all,
I found like top command could be used to find the Memory and CPU utilization. But i want to know how to find the Memory and CPU utilization for a particular user using top command.
Thanks in advance.
Thanks,
Ananthi.U (2 Replies)
Discussion started by: ananthi_ku
2 Replies
5. Solaris
Iostat inquiry;# iostat -e
---- errors ---
device s/w h/w trn tot
fd0 0 0 0 0
md0 0 0 0 0
md1 0 0 0 0
md2 0 0 0 0
md10 0 0 0 0
md11 0 0 0 0
md12 0 0 0 0
md30 0 0 0 0
md31 0 0 0 0
md32 0 0 0 0
md40 0 0 0 0
md41 0 0 0 0
md42 0 0 0 0
md50 0 0 0 0
md51 0 0 0 0
md52 0 0 0 0
md60 0 0 0... (2 Replies)
Discussion started by: pepi
2 Replies
6. Solaris
Hello everyone,
Can you please explain me what kind of information do IOSTAT show ?
iostat -xnz 3 show me those informations:
The I/O of the c0t0d0 disk is normal ?
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 ... (3 Replies)
Discussion started by: adilyos
3 Replies
7. Solaris
Hi Everyone,
I try to calculate the total hard disk space of a solaris machine using iostat -En command. Iterating the output and summing up all the number present near the Size: will give the exact size of the harddisk. But it is not working for a machine.
This command works in many flavors... (2 Replies)
Discussion started by: prasankn
2 Replies
8. SuSE
Hi,
my os is SLES 10
from sort
iostat
as my output does not include rkB/s and wkB/s I probably have to adjust the key position, so
is the following iostat pipe to sort service request command correct?
oracle@vmc_stallite:~> iostat -x | sort -nrk11
sda 0.96 ... (4 Replies)
Discussion started by: jediwannabe
4 Replies
9. Shell Programming and Scripting
Hi,
I have a requirement where parsed output from various linux commands like top, netstat, iostat, etc. will be the input for one javascript with the parsed output from these commands converted to JSON format
For "iostat" command, since there are two outputs - one w.r.t CPU utilization and... (2 Replies)
Discussion started by: gopivallabha
2 Replies
10. Shell Programming and Scripting
Hi,
I got the code below is one of the threads from this forum.
lineCount=$(iostat | wc -l)
numDevices=$(expr $lineCount - 7);
iostat $interval -x -t |
awk -v awkCpuFile=$cpuFile -v awkDeviceFile=$deviceFile -v awkNumDevices=$numDevices '
BEGIN {
print... (2 Replies)
Discussion started by: gopivallabha
2 Replies
LEARN ABOUT SUNOS
drv_usecwait
drv_usecwait(9F) Kernel Functions for Drivers drv_usecwait(9F)
NAME
drv_usecwait - busy-wait for specified interval
SYNOPSIS
#include <sys/types.h>
#include <sys/ddi.h>
void drv_usecwait(clock_t microsecs);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI).
PARAMETERS
microsecs The number of microseconds to busy-wait.
DESCRIPTION
drv_usecwait() gives drivers a means of busy-waiting for a specified microsecond count. The amount of time spent busy-waiting may be
greater than the microsecond count but will minimally be the number of microseconds specified.
delay(9F) can be used by a driver to delay for a specified number of system ticks, but it has two limitations. First, the granularity of
the wait time is limited to one clock tick, which may be more time than is needed for the delay. Second, delay(9F) may only be invoked
from user context and hence cannot be used at interrupt time or system initialization.
Often, drivers need to delay for only a few microseconds, waiting for a write to a device register to be picked up by the device. In this
case, even in user context, delay(9F) produces too long a wait period.
CONTEXT
drv_usecwait() can be called from user or interrupt context.
SEE ALSO
delay(9F), timeout(9F), untimeout(9F)
Writing Device Drivers
NOTES
The driver wastes processor time by making this call since drv_usecwait() does not block but simply busy-waits. The driver should only make
calls to drv_usecwait() as needed, and only for as much time as needed. drv_usecwait() does not mask out interrupts.
SunOS 5.10 12 Nov 1992 drv_usecwait(9F)