From: Oleg Drokin <green@namesys.com>
To: Voicu Liviu <liviu.voicu@huji.ac.il>
Cc: ookhoi@humilis.net, reiserfs-list@namesys.com
Subject: Re: ReiserFS causes CPU high usage?!
Date: Fri, 28 Feb 2003 17:07:37 +0300 [thread overview]
Message-ID: <20030228170737.B11516@namesys.com> (raw)
In-Reply-To: <200302281511.56997.liviu.voicu@huji.ac.il>
Hello!
On Fri, Feb 28, 2003 at 03:11:56PM +0200, Voicu Liviu wrote:
> > You said you had problem with that too, but that is really weird as X
> > would not want 100% cpu.
> > In an other mail you write that your compiles are very fast. If a new
> > kernel doesn't solve your problem, and compiles are very fast anyway, I
> > would say: don't do that then (the renice to -10), or renice to -5 or
> > some value which does not bother you.
> I don't want to renice compilation threads, only X to get more responsives
> from it...but this locks me out :-)
Hm, but if you do not renice X, it works ok?
I just noticed:
> Mem: 255948k av, 250540k used, 5408k free, 0k shrd, 28344k buff
> 59512k active, 119096k inactive
> Swap: 514072k av, 144k used, 513928k free 122280k
So if you add X and kde (and other heavy stuff to that), you basically have no RAM,
so probably all the slowdown is from constant swapping.
Just run top when you see the interactive slowdown and look at the swapin/swapout ratio
and swap isage in top & /proc/stat
Bye,
Oleg
next prev parent reply other threads:[~2003-02-28 14:07 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:11 ReiserFS causes CPU high usage?! Voicu Liviu
2003-02-28 7:51 ` Oleg Drokin
2003-02-28 12:03 ` Voicu Liviu
2003-02-28 12:24 ` Ookhoi
2003-02-28 12:35 ` Voicu Liviu
2003-02-28 12:35 ` Ookhoi
2003-02-28 12:39 ` Voicu Liviu
2003-02-28 12:38 ` Ookhoi
2003-02-28 12:42 ` Voicu Liviu
2003-02-28 12:45 ` Ookhoi
2003-02-28 12:54 ` Voicu Liviu
2003-02-28 13:00 ` Ookhoi
2003-02-28 13:04 ` Voicu Liviu
2003-02-28 13:13 ` Voicu Liviu
2003-02-28 13:26 ` Ookhoi
2003-02-28 13:33 ` Voicu Liviu
2003-02-28 13:33 ` Ookhoi
2003-02-28 13:45 ` Voicu Liviu
2003-02-28 13:48 ` Ookhoi
2003-02-28 13:52 ` Voicu Liviu
2003-02-28 14:02 ` Oleg Drokin
2003-02-28 14:08 ` Voicu Liviu
2003-02-28 12:48 ` Voicu Liviu
2003-02-28 12:56 ` Hans Reiser
2003-02-28 12:57 ` Ookhoi
2003-02-28 13:01 ` Voicu Liviu
2003-02-28 13:37 ` Manuel Krause
2003-02-28 12:56 ` Ookhoi
2003-02-28 13:00 ` Voicu Liviu
2003-02-28 13:06 ` Ookhoi
2003-02-28 13:11 ` Voicu Liviu
2003-02-28 13:13 ` Ookhoi
2003-02-28 13:19 ` Voicu Liviu
2003-02-28 13:32 ` Ookhoi
2003-02-28 13:36 ` Voicu Liviu
2003-02-28 13:33 ` Hans Reiser
2003-02-28 13:39 ` Voicu Liviu
2003-02-28 14:07 ` Oleg Drokin [this message]
2003-02-28 14:12 ` Voicu Liviu
2003-02-28 14:16 ` Oleg Drokin
2003-02-28 13:10 ` Dieter Nützel
2003-02-28 14:57 ` John Dalbec
2003-02-28 16:43 ` Jeff Mahoney
2003-03-01 15:40 ` Vladimir Karavelov
2003-03-01 18:03 ` Voicu Liviu
2003-02-28 12:07 ` Hans Reiser
2003-02-28 12:11 ` Voicu Liviu
2003-02-28 12:13 ` Marc-Christian Petersen
2003-02-28 12:19 ` Voicu Liviu
2003-02-28 12:23 ` Szabolcs Szasz
2003-02-28 12:56 ` Voicu Liviu
2003-02-28 13:02 ` Szabolcs Szasz
2003-02-28 12:25 ` Toby Dickenson
2003-02-28 12:34 ` Voicu Liviu
2003-02-28 12:34 ` Marc-Christian Petersen
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=20030228170737.B11516@namesys.com \
--to=green@namesys.com \
--cc=liviu.voicu@huji.ac.il \
--cc=ookhoi@humilis.net \
--cc=reiserfs-list@namesys.com \
/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.