Date: Mon, 9 May 2005 14:36:32 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Suleiman Souhlal <ssouhlal@freebsd.org> Cc: Pete French <petefrench@ticketswitch.com> Subject: Re: Performance issue Message-ID: <Pine.GSO.4.43.0505091428460.27904-100000@sea.ntplx.net> In-Reply-To: <2B4490FF-FEFD-473F-BDF0-293C468A55B9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0505091428460.27904-100000>