public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Walker <neil@ep.mine.nu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CPU "choking" under high load
Date: Fri, 26 Mar 2010 21:36:06 +0000	[thread overview]
Message-ID: <4BAD28C6.408@ep.mine.nu> (raw)
In-Reply-To: <201003262047.55200.expendable.0@danielquinn.org>

On 26/03/10 20:47, Daniel Quinn wrote:
> I don't know why it's happening.  I've tried various kernel options with no 
> change in behaviour.  Outside of that though, I don't know what to try.  
> Suggestions welcome :-(
>   

It sounds very much to me like a lack of physical memory and your
system is resorting to the swap partition. What does free report?


Be lucky,

Neil
http://www.neiljw.net/


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





  parent reply	other threads:[~2010-03-26 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 20:47 [gentoo-user] CPU "choking" under high load Daniel Quinn
2010-03-26 20:48 ` Kyle Bader
2010-03-26 21:36 ` Neil Walker [this message]
2010-03-26 22:43 ` Dale
2010-03-26 22:52   ` Paul Hartman
2010-03-26 23:37     ` Johannes Kimmel
2010-03-26 22:50 ` Paul Hartman

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=4BAD28C6.408@ep.mine.nu \
    --to=neil@ep.mine.nu \
    --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