public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: warudkar@vsnl.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4-mm1 - kswap hogs cpu OO takes ages to start!
Date: Wed, 27 Aug 2003 04:18:59 -0700	[thread overview]
Message-ID: <20030827111859.GA4306@holomorphy.com> (raw)
In-Reply-To: <200308272138.h7RLciK29987@webmail2.vsnl.net>

On Wed, Aug 27, 2003 at 04:38:44PM -0500, warudkar@vsnl.net wrote:
> Here a snapshot of Top output when running 2.6.0-test4-mm1:
> ==============================
>   4:24pm  up 21:19,  6 users,  load average: 3.47, 2.04, 1.49
> 96 processes: 88 sleeping, 8 running, 0 zombie, 0 stopped
> CPU states: 11.3% user, 88.6% system,  0.0% nice,  0.0% idle
> Mem:   124632K av,  122664K used,    1968K free,       0K shrd,     160K buff
> Swap: 1052248K av,   71256K used,  980992K free                   43540K cached
> 
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>     8 root      15   0     0    0     0 SW   66.6  0.0   4:59 kswapd0
>  2087 wipro     17   0 29576  10M 27408 S     4.6  8.9   0:03 kdeinit
>  2044 wipro     17   0  118M  22M  103M D     2.7 18.8   0:04 soffice.bin

This looks odd. At any rate, the 71MB swap should be a big hint you're
in for slow times. 2.4.x likely does okay here because the virtualscan
acts as implicit load control; 2.6.x will likely need explicit load
control to handle that workload on that machine.


-- wli

  reply	other threads:[~2003-08-27 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 21:38 2.6.0-test4-mm1 - kswap hogs cpu OO takes ages to start! warudkar
2003-08-27 11:18 ` William Lee Irwin III [this message]
2003-08-27 11:30 ` William Lee Irwin III
2003-08-27 11:37 ` Con Kolivas
2003-08-27 19:53   ` Andrew Morton
2003-08-28  2:11     ` Con Kolivas
2003-08-31 16:06       ` Rik van Riel
2003-08-28  3:23     ` Tariq Firoz
2003-08-27 12:17 ` Jose Luis Domingo Lopez

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=20030827111859.GA4306@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warudkar@vsnl.net \
    /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