From: Ookhoi <ookhoi@humilis.net>
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 13:56:05 +0100 [thread overview]
Message-ID: <20030228135605.F24291@humilis> (raw)
In-Reply-To: <200302281448.20572.liviu.voicu@huji.ac.il>
Voicu Liviu wrote (ao):
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> OK, so in this mashine I compile kde3.1 and this is the output of the "top"
> command ( it took me 5 seconds to write top in the command line and another
> 10 antill I saw the output...really slow )
>
> 35 processes: 31 sleeping, 4 running, 0 zombie, 0 stopped
> CPU states: 99.4% user, 0.3% system, 0.0% nice, 0.0% iowait, 0.1% idle
> Mem: 255948k av, 250540k used, 5408k free, 0k shrd, 28344k buff
> 59512k active, 119096k inactive
> Swap: 514072k av, 144k used, 513928k free 122280k
> cached
>
> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
> 889 portage 15 -10 21508 21M 4172 R < 98.9 8.4 0:16 cc1plus
> 890 portage 5 -10 2368 2368 752 S < 0.9 0.9 0:00 as
> 845 liviu 15 0 1100 1100 792 R 0.1 0.4 0:00 top
> 1 root 15 0 484 484 428 S 0.0 0.1 0:05 init
In your case, there is no reason to renice the compile to -10, as there
are no other processes which take cpu, and therefore there is nothing to
gain.
I still wonder what could be the reason for the bad response of the
keyboard.
next prev parent reply other threads:[~2003-02-28 12:56 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 [this message]
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
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=20030228135605.F24291@humilis \
--to=ookhoi@humilis.net \
--cc=liviu.voicu@huji.ac.il \
--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.