From owner-freebsd-questions@FreeBSD.ORG Wed Apr 14 20:03:17 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC5B016A4CE for ; Wed, 14 Apr 2004 20:03:17 -0700 (PDT) Received: from plewe.is.tsukuba.ac.jp (plewe.is.tsukuba.ac.jp [130.158.81.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0673B43D45 for ; Wed, 14 Apr 2004 20:03:16 -0700 (PDT) (envelope-from till@plewe.is.tsukuba.ac.jp) Received: from plewe.is.tsukuba.ac.jp (localhost [127.0.0.1]) i3F38XSU027279 for ; Thu, 15 Apr 2004 12:08:33 +0900 (JST) (envelope-from till@plewe.is.tsukuba.ac.jp) Received: (from till@localhost) by plewe.is.tsukuba.ac.jp (8.12.11/8.12.11/Submit) id i3F38X1m027278 for freebsd-questions@freebsd.org; Thu, 15 Apr 2004 12:08:33 +0900 (JST) (envelope-from till) Date: Thu, 15 Apr 2004 12:08:33 +0900 From: Till Plewe To: freebsd-questions@freebsd.org Message-ID: <20040415030833.GB27152%till@score.is.tsukuba.ac.jp> Mail-Followup-To: freebsd-questions@freebsd.org References: <20040415025938.GA27152%till@score.is.tsukuba.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040415025938.GA27152%till@score.is.tsukuba.ac.jp> User-Agent: Mutt/1.5.4i-ja.1 Subject: Re: second CPU not utilized X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: till@score.is.tsukuba.ac.jp List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2004 03:03:18 -0000 On Thu, Apr 15, 2004 at 11:59:38AM +0900, Till Plewe wrote: > > Does anybody have an idea why the second cpu is not used for the > computing intensive work? > > idle will stay around 50% while the two instances of python2.4 share 1 CPU > > The only unusual occurence recently were a few Bus Errors and the system freezing > when two processes which were using around 2-4GB of memory each were running I forgot to mention that until the system froze last night both instances were running at 99% using both CPUs. The current behaviour started after rebooting. - Till