Date: Thu, 19 Aug 1999 03:01:22 -0700 (PDT) From: holger.kipp@solit-ag.de To: freebsd-gnats-submit@freebsd.org Subject: kern/13252: niced jobs don't behave really nice Message-ID: <19990819100122.5A55715085@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 13252 >Category: kern >Synopsis: niced jobs don't behave really nice >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Aug 19 03:10:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Holger Kipp >Release: 2.2.8 >Organization: SolIT AG >Environment: FreeBSD intserv 2.2.8-RELEASE FreeBSD 2.2.8-RELEASE #0: Tue Jan 26 23:44:04 CET 1999 root@intserv:/usr/src/sys/compile/INTSERV i386 >Description: Niced jobs use up to much CPU time if other jobs are running (or are supposed to be running instead). >How-To-Repeat: Run some timecritical software (eg amanda) and install some other jobs that are supposed to _really_ run in the background (ie start them with nice -19). Specifically suited are CRACK and SETI@home. Then have a look at the jobs with top and see the niced jobs running with > 80% CPU usage even though amanda with dumper and gzip are running... >Fix: No idea, but under my Linux implementation "Linux clausthal 2.0.36 #5 Wed Jan 20 14:23:31 MET 1999 i686 unknown" I tested this with SETI@home with nice -19, and there was no slowdown whatsoever noticeable if running other processes. The niced SETI@home job is really only using the CPU-time the idle-process would otherwise use. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990819100122.5A55715085>