From owner-freebsd-current Sat May 27 12:39:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 278FB37B94B for ; Sat, 27 May 2000 12:39:36 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA89771; Sat, 27 May 2000 12:38:36 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <3930243C.CBAA911E@gorean.org> Date: Sat, 27 May 2000 12:38:36 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0526 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jacob A. Hart" Cc: Sheldon Hearn , FreeBSD-CURRENT Subject: Re: Scheduler changes? References: <20000526131949.A9232@carcass.au.hartware.com> <74533.959349665@axl.ops.uunet.co.za> <20000527173624.A207@carcass.au.hartware.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jacob A. Hart" wrote: > > On Fri, May 26, 2000 at 04:01:05PM +0200, Sheldon Hearn wrote: > > > > > > On Fri, 26 May 2000 13:19:49 +1000, "Jacob A. Hart" wrote: > > > > > For the past couple of weeks I've noticed rc5des isn't playing friendly with > > > the other processes on my system. When running a CPU intensive task (such > > > as a buildworld, MP3 encoder, or xmame) rc5des hogs around 20-30% CPU even > > > though, by default, it is niced at +20. > > > > As a datapoint, I have a one week old (2000-05-18) CURRENT box that runs > > setiathome all day every day. When builds kick in, setiathome gets > > relagated to the single-digit percentiles in top's display of CPU users. > > This is only true when serious building is happening; those aspects of > > the build that I can imagine are more I/O than CPU intensive give > > setiathome a fighting chance. Try setting the nice value for rc5 to something lower than 20, but higher than the highest (lowest) value running on your system. There was a bug with the scheduler in the past that items run at nice 20 were actually getting more cpu than they were supposed to. If this change fixes things for you, please report it asap, since my understanding is that this problem is rather elusive and annoying. Thanks, Doug -- "Live free or die" - State motto of my ancestral homeland, New Hampshire Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message