From owner-freebsd-stable@FreeBSD.ORG  Mon May  9 18:36:33 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 E13CD16A4EB; Mon,  9 May 2005 18:36:33 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4E63943D54; Mon,  9 May 2005 18:36:33 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	j49IaW7s001123;	Mon, 9 May 2005 14:36:32 -0400 (EDT)
Date: Mon, 9 May 2005 14:36:32 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Suleiman Souhlal <ssouhlal@freebsd.org>
In-Reply-To: <2B4490FF-FEFD-473F-BDF0-293C468A55B9@FreeBSD.org>
Message-ID: <Pine.GSO.4.43.0505091428460.27904-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
cc: ewan@mathcode.net
cc: freebsd-stable@freebsd.org
cc: Pete French <petefrench@ticketswitch.com>
Subject: Re: Performance issue
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2005 18:36:34 -0000

On Mon, 9 May 2005, Suleiman Souhlal wrote:
> Hello,
>
>
> I ran ktrace(1) on it, and it appears that python keeps calling
> sigprocmask() continually:
>
>     673 python   0.000007 CALL  sigprocmask(0x3,0,0x811d11c)
>     673 python   0.000005 RET   sigprocmask 0
>     673 python   0.000009 CALL  sigprocmask(0x1,0,0x8113d1c)
>     673 python   0.000005 RET   sigprocmask 0
> etc..
>
> This explains why it's using so much system time. Now the question is
> why is python doing this?

I don't know what python's doing, but it might not be calling
sigprocmask directly.  There are a few libc functions that use
sigprocmask:

	db/btree/
	db/hash/
	pselect(),
	setmode(),
	{sig}setjmp(), {sig}longjmp(),
	grantpt(),
	system()

to name a few.  Python may also be using other libraries which
use sigprocmask().

-- 
DE