03-24-2011
It would help to know what those statistics are. But in general there are counters in the kernel that record interesting events. If the counter is at, say, 8000, at one time and then 8200 ten seconds later, we know that 200 things happened in the last 10 seconds. But what is the counter is a 16 bit counter and it is at 65000 at the first reading and then 125 ten seconds later? The counter rolled. This screws up the math.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
We like to know if there is a way to report the sar -q per processor on AIX 4.3 .
Please help
RGDS,Elie. (1 Reply)
Discussion started by: eyounes
1 Replies
2. UNIX for Advanced & Expert Users
I am trying to collect the sar output for around 90minutes.
When i do
sar 1 5000 >> /tmp/sar.out
It's not updating the sar.out file. When we decrease the 5000 to smaller number like 10, i can see the file sar.out updated after the 10seconds.If i kill my sar while it is running it's not... (1 Reply)
Discussion started by: skneeli
1 Replies
3. HP-UX
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)
Discussion started by: Ashrunil
3 Replies
4. Shell Programming and Scripting
Hi All,
i tried sar command the output appears to be for several days
I would like to just see today's SAR output: Please advice me.
$sar
Linux 2.6.9-67.ELsmp (lrtp50) 02/28/09
00:00:01 CPU %user %nice %system %iowait %idle
00:05:02 all 3.10... (4 Replies)
Discussion started by: raghur77
4 Replies
5. Shell Programming and Scripting
Hi,
We have 2 scripts below for reporting sar output which are pretty same.
In first script i want to add to the program whatever is given in the comments.
In second script I want to use while true to run this program every hour and everything that is in comment.
Finally I want to club... (0 Replies)
Discussion started by: noorm
0 Replies
6. Solaris
Hi,
Anyone knows how to extract sar command output to excel or Is there any free grapical tools to extract this sar log file. thanks, regards (2 Replies)
Discussion started by: vijill
2 Replies
7. Solaris
One of my servers giving all zero sar output. Could anyone explain this behaviour.
Thanks
CHaandana
Sample:
10:43:37 %usr %sys %wio %idle
16:15:01 2 1 0 97
16:20:02 2 1 0 97
16:25:02 2 1 0 97
16:30:01 ... (3 Replies)
Discussion started by: chaandana
3 Replies
8. Shell Programming and Scripting
Hi
I have an output of sarcommand which is as follows:
10:22:18 bread/s lread/s %rcache bwrit/s lwrit/s %wcache pread/s pwrit/s
10:23:18 0 398 100 5 13 64 0 0
10:24:18 0 332 100 5 15 65 0 0
10:25:18 0 ... (7 Replies)
Discussion started by: fretagi
7 Replies
9. Solaris
We're experiencing some intermittent freezes on one of our systems and I'm trying to figure out what is happening.
We're running Solaris 10 zones mounting shares from netapp through nfs.
On the zone that freezes we have sar running and are getting this output:
SunOS prodserver 5.10... (3 Replies)
Discussion started by: Jyda
3 Replies
10. Red Hat
I am facing situation where sar -u command is showing 0 for all cps, so does it mean all the cpus are fully utilized, os is oracle Linux 6.8
01:34:13 PM all 0 0 0 0 0.00 0 (2 Replies)
Discussion started by: manoj.solaris
2 Replies
LEARN ABOUT FREEBSD
timecounters
TIMECOUNTERS(4) BSD Kernel Interfaces Manual TIMECOUNTERS(4)
NAME
timecounters -- kernel time counters subsystem
SYNOPSIS
The kernel uses several types of time-related devices, such as: real time clocks, time counters and event timers. Real time clocks are
responsible for tracking real world time, mostly when the system is down. Time counters are responsible for tracking purposes, when the sys-
tem is running. Event timers are responsible for generating interrupts at a specified time or periodically, to run different time-based
events. This page is about the second.
DESCRIPTION
Time counters are the lowest level of time tracking in the kernel. They provide monotonically increasing timestamps with known width and
update frequency. They can overflow, drift, etc and so in raw form can be used only in very limited performance-critical places like the
process scheduler.
More usable time is created by scaling the values read from the selected time counter and combining it with some offset, regularly updated by
tc_windup() on hardclock() invocation.
Different platforms provide different kinds of timer hardware. The goal of the time counters subsystem is to provide a unified way to access
that hardware.
Each driver implementing time counters registers them with the subsystem. It is possible to see the list of present time counters, via the
kern.timecounter sysctl(8) variable:
kern.timecounter.choice: TSC-low(-100) HPET(950) i8254(0) ACPI-fast(900) dummy(-1000000)
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.ACPI-fast.counter: 13467909
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.quality: 900
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.i8254.counter: 62692
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.HPET.counter: 3013495652
kern.timecounter.tc.HPET.frequency: 14318180
kern.timecounter.tc.HPET.quality: 950
kern.timecounter.tc.TSC-low.mask: 4294967295
kern.timecounter.tc.TSC-low.counter: 4067509463
kern.timecounter.tc.TSC-low.frequency: 11458556
kern.timecounter.tc.TSC-low.quality: -100
The output nodes are defined as follows:
kern.timecounter.tc.X.mask is a bitmask, defining valid counter bits,
kern.timecounter.tc.X.counter is a present counter value,
kern.timecounter.tc.X.frequency is a counter update frequency,
kern.timecounter.tc.X.quality is an integral value, defining the quality of this time counter compared to others. A negative value means
this time counter is broken and should not be used.
The time management code of the kernel chooses one time counter from that list. The current choice can be read and affected via the
kern.timecounter.hardware tunable/sysctl.
SEE ALSO
attimer(4), eventtimers(4), ffclock(4), hpet(4)
BSD
April 12, 2014 BSD