From owner-freebsd-bugs Fri Jun 25 11:46:18 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6D53C14E75 for ; Fri, 25 Jun 1999 11:46:14 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA13709; Fri, 25 Jun 1999 20:46:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Thomas Schuerger Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/12381: Bad scheduling in FreeBSD In-reply-to: Your message of "Fri, 25 Jun 1999 11:40:03 PDT." <199906251840.LAA34516@freefall.freebsd.org> Date: Fri, 25 Jun 1999 20:46:06 +0200 Message-ID: <13707.930336366@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199906251840.LAA34516@freefall.freebsd.org>, Thomas Schuerger write s: > > Basically, you want renice 20 pid to cause the affected pid to be > > allowed as close to no CPU time as possible while there are > > compute-bound processes at nice <20 running. > > > > Is this right? > > Yes, that's what I meant by bad scheduling. > > I think the nice-level only has a very minor effect in FreeBSD, which > is not what I expect in a Unix environment. What it means is that there is > no possibility to really run processes "in the background", e.g. sort of > in the "spare time" of the CPU (these processes still should become active every > now and then when more important processes are running, completely cutting them > off would not be what I'd want). Something like an exponential drop off with > increasing nice-levels would be fine, for example. In fact there is a way to do this, look at the rtprio man page. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message