On 22/11/2007, Raj Mathur [EMAIL PROTECTED] wrote:
If you want to see this in action, do the following on a relatively
unloaded system:
- - Open up one terminal and run: sar -u 1 1
- - Open up another terminal and run: ls -lR / /dev/null
Watch the %iowait times in the sar output go up
From the man pages of uptime, you get
Print the current time, the length of time the system has been up,
the number of users on the system, and the average number of jobs
in the run queue over the last 1, 5 and 15 minutes.
The above does not seem to match on my system (Ubuntu Feisty).
$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
,--[ On Wed, Nov 21, 2007 at 12:42:13PM +, Yashpal Nagar wrote:
| Hi All,
|
| From the man pages of uptime, you get
|
| Print the current time, the length of time the system has been up,
| the number of users on the system, and the average
On Wednesday 21 Nov 2007, Yashpal Nagar wrote:
Hi All,
From the man pages of uptime, you get
Print the current time, the length of time the system has been up,
the number of users on the system, and the average number of jobs
in the run queue over the last 1, 5 and 15 minutes.
But when
Saleem Ansari wrote:
Read here for detailed explanation of Load Averages.
http://www.teamquest.com/resources/gunther/display/5/index.htm
Very interesting to know the difference between cpu utilization and
load.
Do you also know where are the Dr. Gunther's Quiz answers?
Raj Mathur wrote:
So in a sense the load average is a measure of the load on the system.
Higher load averages mean that the processor is unable to handle the
demands put onto it by the tasks running in the system. However,
there are no fixed measures for defining what load average is high
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 22 Nov 2007, Yashpal Nagar wrote:
Raj Mathur wrote:
So in a sense the load average is a measure of the load on the
system. Higher load averages mean that the processor is unable to
handle the demands put onto it by the tasks running
On 22/11/2007, Raj Mathur [EMAIL PROTECTED] wrote:
[snip]
So to sum up:
Times when the CPU is executing user code is counted in %user.
Times when the CPU is executing a system call (or running any other
kernel code) is counted in %system.
Times when the CPU is waiting for some I/O to
hi all
good day
i want to a used(6 month) laptop
if any one have and want to sell than tellme
___
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Next Event: http://freed.in - February 22/23, 2008
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 22 Nov 2007, Kazim Zaidi wrote:
On 22/11/2007, Raj Mathur [EMAIL PROTECTED] wrote:
[snip]
So to sum up:
Times when the CPU is executing user code is counted in %user.
Times when the CPU is executing a system call (or running any
10 matches
Mail list logo
