From owner-freebsd-stable@FreeBSD.ORG Mon May 9 19:43:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74F1416A4EC for ; Mon, 9 May 2005 19:43:46 +0000 (GMT) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97ADC43D80 for ; Mon, 9 May 2005 19:43:45 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j49JhhAg012600 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 May 2005 05:43:43 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j49JhgPL000280; Tue, 10 May 2005 05:43:42 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j49Jhg43000279; Tue, 10 May 2005 05:43:42 +1000 (EST) (envelope-from pjeremy) Date: Tue, 10 May 2005 05:43:41 +1000 From: Peter Jeremy To: Ewan Todd Message-ID: <20050509194341.GA226@cirb503493.alcatel.com.au> References: <20050509150018.GF281@mathcode.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050509150018.GF281@mathcode.net> User-Agent: Mutt/1.4.2i cc: freebsd-stable Subject: Re: Performance issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2005 19:43:46 -0000 On Mon, 2005-May-09 11:00:18 -0400, Ewan Todd wrote: >I have what I think is a serious performance issue with fbsd 5.3 >release. I've read about threading issues, and it seems to me that >that is what I'm looking at, but I'm not confident enough to rule out >that it might be a hardware issue, a kernel configuration issue, or >something to do with the python port. There does appear to be a problem in FreeBSD. Python is built with threading enabled by default, the threading libraries play with the signal mask and there have been extensive changes there. My suggestions on things you could check are: 1) Rebuild python with threading disabled (add '-DWITHOUT_THREADS' to the 'make' command line and see if that makes any difference 2) Re-write the sample program in a non-threaded language - eg C or perl and see if the high system time goes away. Unfortunately, I can't think of a solution at present. -- Peter Jeremy