All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Russell Coker <russell@coker.com.au>
Cc: flx@msu.ru, ReiserFS <reiserfs-list@namesys.com>
Subject: Re: kernel go-slow
Date: Thu, 6 Feb 2003 19:48:03 +0300	[thread overview]
Message-ID: <20030206194803.A2637@namesys.com> (raw)
In-Reply-To: <200302061741.46153.russell@coker.com.au>

Hello!

On Thu, Feb 06, 2003 at 05:41:46PM +0100, Russell Coker wrote:

> > but there is possible situations that will not generate disk activity,
> > but may cause your system to "go-slow", if there you have some
> > unussual IO numbers while disk activity is moderate to low -
> > most likely same sweet pair.
> The problem is that sar etc product jumbled results.  Profiling the kernel may 
> help, but may also hide the error, and it's not something I can easily do.

Well, you can do it very easily.
reboot with "profile=2" kernel option.
when 100% sys cpu situation started - execute readprofile -r
when it is finished, execute readprofile -m /path/to/System.map >somefile
then sort somefile and you are done, you are now seeing where is most of the time
is spent.

> The servers are locked in a managed server room on the other side of the city 
> so seeing the blinken lights is not an option.

;)
<humour>webcam</humour>

> I've put the aa1 kernel on half the machines and now I'll wait to see what 
> happens.  If the aa1 machines don't have the problem but the others do then 
> I'll go all aa1.

Ah, if your problem was with highmem I/O not present, then that might actually help.

Bye,
    Oleg

  reply	other threads:[~2003-02-06 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 23:27 kernel go-slow Russell Coker
2003-02-02 23:42 ` Rudy L. Zijlstra
2003-02-03  4:53 ` Ookhoi
2003-02-06 11:26 ` Alexander Lyamin
2003-02-06 16:32   ` Alexander Lyamin
2003-02-06 16:41     ` Russell Coker
2003-02-06 16:48       ` Oleg Drokin [this message]
2003-02-06 18:58       ` Hans Reiser

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=20030206194803.A2637@namesys.com \
    --to=green@namesys.com \
    --cc=flx@msu.ru \
    --cc=reiserfs-list@namesys.com \
    --cc=russell@coker.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.