public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: sean <tech.junk@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Excessive processor usage
Date: Mon, 06 Aug 2007 07:50:33 -0400	[thread overview]
Message-ID: <46B70B09.7010909@verizon.net> (raw)

There seems to be a lot of excessive processor usage and I am trying to 
track down why.

Is anyone able to recommend the best way to track down what is causing 
the excess processor usage?

I have not noticed anything using top.

					Thanks
					Sean

-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2007-08-06 11:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 11:50 sean [this message]
2007-08-06 11:56 ` [gentoo-user] Excessive processor usage Xav'
2007-08-06 12:55   ` sean
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=46B70B09.7010909@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