From owner-freebsd-current Fri May 26 7: 2:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 7672137BBB6 for ; Fri, 26 May 2000 07:02:04 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12vKfh-000JOA-00; Fri, 26 May 2000 16:01:05 +0200 From: Sheldon Hearn To: "Jacob A. Hart" Cc: FreeBSD-CURRENT Subject: Re: Scheduler changes? In-reply-to: Your message of "Fri, 26 May 2000 13:19:49 +1000." <20000526131949.A9232@carcass.au.hartware.com> Date: Fri, 26 May 2000 16:01:05 +0200 Message-ID: <74533.959349665@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message