Date: Sun, 25 Feb 2007 23:40:37 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Martin Blapp <mb@imp.ch> Cc: Daniel Eischen <deischen@freebsd.org>, rob@debank.tv, freebsd-threads@freebsd.org Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so Message-ID: <20070226074037.GJ73385@funkthat.com> In-Reply-To: <20070224185741.F18301@godot.imp.ch> References: <20070220190347.C4139@godot.imp.ch> <Pine.GSO.4.64.0702201319230.12034@sea.ntplx.net> <20070220225303.V4139@godot.imp.ch> <Pine.GSO.4.64.0702201724590.12034@sea.ntplx.net> <20070220234734.H4139@godot.imp.ch> <20070221000830.V4139@godot.imp.ch> <20070221020335.Y4139@godot.imp.ch> <20070224103422.V18301@godot.imp.ch> <Pine.GSO.4.64.0702241012230.5266@sea.ntplx.net> <20070224185741.F18301@godot.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
Martin Blapp wrote this message on Sat, Feb 24, 2007 at 19:06 +0100:
> >>Running ktrace with libc_r or libthr I can't see a single call to fork().
> >>Is ktrace lying to me ? Why do I only see fork()s with libpthread ?
> >
> >The kse upcalls might look like forks to ktrace?
> >
>
> That could be. Is it easy to fix this for ktrace ?
>
> Anyway, that still doesn't solve the problem for me, since
> clamd with libpthreads is extremly CPU hungry and is slow.
>
> I really miss something to profile like strace on solaris to
> see where it spends most CPU cycles. The problem is not that
> it doesn't work, the problem is that it works far too slow.
Have you tried using pmc? Works at full processor speed...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070226074037.GJ73385>