From: sean <tech.junk@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Excessive processor usage
Date: Mon, 06 Aug 2007 08:55:27 -0400 [thread overview]
Message-ID: <46B71A3F.9050309@verizon.net> (raw)
In-Reply-To: <46B70C70.5070600@linuxant.fr>
Xav' wrote:
> So how do you know there is an excessive processor usage ? Could you describe
> more precisely what you want to mean ?
Have gkrellm2 monitoring CPU usage and often for varied lengths of time
will see a long and increased processor usage, this usually occurs on CPU1.
Things get a bit sluggish when this happens. This is a recent problem.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-08-06 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 11:50 [gentoo-user] Excessive processor usage sean
2007-08-06 11:56 ` Xav'
2007-08-06 12:55 ` sean [this message]
2007-08-06 13:55 ` Volker Armin Hemmann
2007-08-06 14:49 ` sean
2007-08-06 12:03 ` Abraham Marín Pérez
2007-08-06 12:30 ` Xav'
2007-08-06 14:29 ` Hans-Werner Hilse
2007-08-06 14:49 ` sean
2007-08-06 15:14 ` Neil Bothwick
2007-08-06 18:09 ` Uwe Thiem
2007-08-06 18:16 ` Paul
2007-08-06 17:36 ` [gentoo-user] " James
2007-08-06 12:30 ` [gentoo-user] " Duane Griffin
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=46B71A3F.9050309@verizon.net \
--to=tech.junk@verizon.net \
--cc=gentoo-user@lists.gentoo.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