From owner-freebsd-current@FreeBSD.ORG Mon May 26 16:49:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27D4337B401; Mon, 26 May 2003 16:49:29 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 935AB43F85; Mon, 26 May 2003 16:49:28 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from dialup-67.30.96.194.dial1.sanjose1.level3.net ([67.30.96.194] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KRiV-00041s-00; Mon, 26 May 2003 16:49:23 -0700 Message-ID: <3ED2A7B7.C3D1553E@mindspring.com> Date: Mon, 26 May 2003 16:48:07 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Martin Blapp References: <20030526175945.R561@cvs.imp.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a468be3c4944b4c29f7301023688a45cfda7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c cc: tegge@freebsd.org cc: current@freebsd.org Subject: Re: linux_threads nice bug ? nice / nohup confusion X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 23:49:29 -0000 Martin Blapp wrote: > After closly looking at some of our mysql performance issues, > I've found out that all mysqld threads (I'm using linuxthreads) > are running at +14 niceness. This is of course a catastropy. > > A renice of the main thread does not help. If I do that, I see > that all new created threads have again niceness +14. Starting > without nohup makes +11 as niceness. > > I guess there is somewhere a severe bug here. Depends; "niceness" is relative to the scheduler you are using. Try using the other scheduler, and this should become pretty obvious to you. -- Terry