linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Cc: Mike Galbraith <efault@gmx.de>, bert hubert <bert.hubert@netherlabs.nl>
Subject: Re: [patch][rfc] quell interactive feeding frenzy
Date: Mon, 10 Apr 2006 17:43:17 +0300	[thread overview]
Message-ID: <200604101743.17518.a1426z@gawab.com> (raw)
In-Reply-To: <1144607596.7408.34.camel@homer>

bert hubert wrote:
> In general, Linux systems are not maxed out as they will disappoint that
> way (like any system running with id=0).

top - 16:59:23 up 29 min,  0 users,  load average: 993.49, 796.33, 496.21
Tasks: 1039 total, 1000 running,  39 sleeping,   0 stopped,   0 zombie
Cpu(s):  47.6% user,  52.4% system,   0.0% nice,   0.0% idle,   0.0% IO-wait
Mem:    125796k total,   123344k used,     2452k free,       64k buffers
Swap:  1020088k total,     9176k used,  1010912k free,     1752k cached

  PID  PR  NI  VIRT  RES  SHR SWAP S %CPU    TIME+  Command
 3946  28   0  2404 1460  720  944 R  5.8   0:14.78 top
 4219  37   0  1580  488  416 1092 R  3.0   0:00.45 ping
 4214  37   0  1584  480  408 1104 R  2.8   0:00.46 ping
 4196  37   0  1580  480  408 1100 R  2.5   0:00.45 ping
 4175  37   0  1584  488  416 1096 R  2.3   0:00.30 ping
 3950  37   1  1580  492  416 1088 R  2.0   0:08.77 ping
 4136  37   0  1580  488  416 1092 R  2.0   0:00.36 ping
 4158  37   0  1584  484  408 1100 R  2.0   0:00.35 ping
 4177  37   0  1580  480  408 1100 R  2.0   0:00.27 ping
 4180  37   0  1580  484  408 1096 R  2.0   0:00.33 ping
 4194  37   0  1580  480  408 1100 R  2.0   0:00.40 ping
 4199  37   0  1584  484  408 1100 R  2.0   0:00.47 ping
 4189  37   0  1580  488  416 1092 R  1.8   0:00.43 ping
 4153  37   0  1584  480  408 1104 R  1.5   0:00.31 ping
 4170  37   0  1584  484  408 1100 R  1.5   0:00.30 ping
 4191  37   0  1584  492  416 1092 R  1.5   0:00.41 ping
 4209  37   0  1584  484  408 1100 R  1.5   0:00.39 ping
 4215  37   0  1584  484  408 1100 R  1.5   0:00.39 ping
 4221  37   0  1580  492  416 1088 R  1.5   0:00.37 ping
 4146  37   0  1580  488  416 1092 R  1.3   0:00.29 ping
 4156  37   0  1584  484  408 1100 R  1.3   0:00.32 ping
 4166  37   0  1584  488  416 1096 R  1.3   0:00.33 ping
 4183  37   0  1580  480  408 1100 R  1.3   0:00.37 ping
 4216  37   0  1584  480  408 1104 R  1.3   0:00.39 ping
 4229  37   0  1584  484  408 1100 R  1.3   0:00.41 ping
 4233  37   0  1584  488  416 1096 R  1.3   0:00.41 ping
 4137  37   0  1580  484  408 1096 R  1.0   0:00.33 ping
 4141  37   0  1584  484  408 1100 R  1.0   0:00.31 ping
 4150  37   0  1580  484  408 1096 R  1.0   0:00.30 ping
 4161  37   0  1580  480  408 1100 R  1.0   0:00.29 ping
 4172  37   0  1584  484  408 1100 R  1.0   0:00.28 ping
 4178  37   0  1580  480  408 1100 R  1.0   0:00.25 ping
 4182  37   0  1584  484  408 1100 R  1.0   0:00.23 ping

After that the loadavg starts to wrap.
And even then it is possible to login.
And that's not with the default 2.6 scheduler, but rather w/ spa.

Thanks!

--
Al




  reply	other threads:[~2006-04-10 14:45 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 16:44 [patch][rfc] quell interactive feeding frenzy Al Boldi
2006-04-09 18:33 ` Mike Galbraith
2006-04-10 14:43   ` Al Boldi [this message]
2006-04-11 10:57     ` Con Kolivas
     [not found] <200604112100.28725.kernel@kolivas.org>
2006-04-11 17:03 ` Fwd: " Al Boldi
2006-04-11 22:56   ` Con Kolivas
2006-04-12  5:41     ` Al Boldi
2006-04-12  6:22       ` Con Kolivas
2006-04-12  8:17         ` Al Boldi
2006-04-12  9:36           ` Con Kolivas
2006-04-12 10:39             ` Al Boldi
2006-04-12 11:27               ` Con Kolivas
2006-04-12 15:25                 ` Al Boldi
2006-04-13 11:51                   ` Con Kolivas
2006-04-14  3:16                     ` Al Boldi
2006-04-15  7:05                       ` Con Kolivas
2006-04-15 20:45                         ` Al Boldi
2006-04-15 23:22                           ` Con Kolivas
2006-04-16  6:02                   ` Con Kolivas
2006-04-16  8:31                     ` Al Boldi
2006-04-16  8:58                       ` Con Kolivas
  -- strict thread matches above, loose matches on Subject: below --
2006-04-07  9:38 Mike Galbraith
2006-04-07  9:47 ` Andrew Morton
2006-04-07  9:52   ` Ingo Molnar
2006-04-07 10:57     ` Mike Galbraith
2006-04-07 11:00       ` Con Kolivas
2006-04-07 11:09         ` Mike Galbraith
2006-04-07 10:40   ` Mike Galbraith
2006-04-07 12:56 ` Con Kolivas
2006-04-07 13:37   ` Mike Galbraith
2006-04-07 13:56     ` Con Kolivas
2006-04-07 14:14       ` Mike Galbraith
2006-04-07 15:16         ` Mike Galbraith
2006-04-09 11:14         ` bert hubert
2006-04-09 11:39           ` Mike Galbraith
2006-04-09 12:14             ` bert hubert
2006-04-09 18:07               ` Mike Galbraith
2006-04-10  9:12                 ` bert hubert
2006-04-10 10:00                   ` Mike Galbraith
2006-04-10 14:56                     ` Mike Galbraith
2006-04-13  7:41                       ` Mike Galbraith
2006-04-13 10:16                         ` Con Kolivas
2006-04-13 11:05                           ` Mike Galbraith
2006-04-09 18:24               ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200604101743.17518.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=bert.hubert@netherlabs.nl \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).