All of lore.kernel.org
 help / color / mirror / Atom feed
From: LA Walsh <law@sgi.com>
To: Quim K Holland <qkholland@my-deja.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] 2.4.x nice level
Date: Mon, 02 Apr 2001 20:02:02 -0700	[thread overview]
Message-ID: <3AC93D2A.760CE67F@sgi.com> (raw)
In-Reply-To: <200104022304.QAA19333@mail6.bigmailbox.com>

Quim K Holland wrote:
> 
> >>>>> "BS" == BERECZ Szabolcs <szabi@inf.elte.hu> writes:
> 
> BS> ... a setiathome running at nice level 19, and a bladeenc at
> BS> nice level 0. setiathome uses 14 percent, and bladeenc uses
> BS> 84 percent of the processor. I think, setiathome should use
> BS> max 2-3 percent.  the 14 percent is way too much for me.
> BS> ...
> BS> with kernel 2.2.16 it worked for me.
> BS> now I use 2.4.2-ac20
---
	I was running 2 copies of setiathome on a 4 CPU server
@ work.  The two processes ran nice'd -19.  The builds we were 
running still took 20-30% longer as opposed to when setiathome wasn't
running (went from 45 minutes up to about an hour).  This machine
has 1G, so I don't think it was hurting from swapping.

I finally wrote a script that checked every 30 seconds -- if the
load on the machine climbed over '4', the script would SIGSTOP the
seti jobs.  Once the load on the machine fell below 2, it would 
send a SIGCONT to them.  

I was also running setiathome on my laptop for a short while --
but the fan kept coming on and the computer would get really hot.
So I stopped that.  Linux @ idle doesn't seem to ever kick on
the fan, but turn on a CPU cruching program and it sure seemed
to heat up the machine.  I still wonder how many kilo or mega watts
go to running dispersed computation programs.  Just one of those
things I may never know....

-l

-- 
The above thoughts and           | They may have nothing to do with
writings are my own.             | the opinions of my employer. :-)
L A Walsh                        | Trust Technology, Core Linux, SGI
law@sgi.com                      | Voice: (650) 933-5338

  reply	other threads:[~2001-04-03  3:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 23:04 [QUESTION] 2.4.x nice level Quim K Holland
2001-04-03  3:02 ` LA Walsh [this message]
     [not found] <fa.j9vo8pv.1rj8up9@ifi.uio.no>
     [not found] ` <fa.dkui9av.1ulsbjm@ifi.uio.no>
2001-04-05 17:24   ` Tor Arntsen
  -- strict thread matches above, loose matches on Subject: below --
2001-04-04 16:12 SodaPop
2001-04-10  3:37 ` george anzinger
2001-04-10 16:10   ` Rik van Riel
2001-04-10 16:39     ` george anzinger
2001-04-02 22:13 BERECZ Szabolcs

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=3AC93D2A.760CE67F@sgi.com \
    --to=law@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qkholland@my-deja.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.