From owner-freebsd-threads@FreeBSD.ORG Sun Feb 25 07:06:00 2007 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED59116A402 for ; Sun, 25 Feb 2007 07:06:00 +0000 (UTC) (envelope-from mb@imp.ch) Received: from pop.imp.ch (mx2.imp.ch [157.161.9.17]) by mx1.freebsd.org (Postfix) with ESMTP id 80BA213C441 for ; Sun, 25 Feb 2007 07:06:00 +0000 (UTC) (envelope-from mb@imp.ch) Received: from dan.imp.ch (godot.imp.ch [157.161.4.8]) by pop.imp.ch (8.13.8/8.13.8/Submit_imp) with ESMTP id l1P75uAl018619 for ; Sun, 25 Feb 2007 08:05:58 +0100 (CET) (envelope-from mb@imp.ch) Date: Sat, 24 Feb 2007 23:24:42 +0100 (CET) From: Martin Blapp To: Daniel Eischen In-Reply-To: Message-ID: <20070224231443.S18301@godot.imp.ch> References: <20070220153632.E4139@godot.imp.ch> <20070220174221.B4139@godot.imp.ch> <20070220190347.C4139@godot.imp.ch> <20070220225303.V4139@godot.imp.ch> <20070220234734.H4139@godot.imp.ch> <20070221000830.V4139@godot.imp.ch> <20070221020335.Y4139@godot.imp.ch> <20070224103422.V18301@godot.imp.ch> <20070224185741.F18301@godot.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed ReSent-Date: Sun, 25 Feb 2007 08:05:52 +0100 (CET) ReSent-From: Martin Blapp ReSent-To: freebsd-threads@freebsd.org ReSent-Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so ReSent-Message-ID: <20070225080552.C18301@godot.imp.ch> Cc: Subject: Re: 6.2-Release and Clamd 0.90 with libpthread.so X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 07:06:01 -0000 Let me make a summary: With kern.threads.virtual_cpu=1 clamd works best with libpthread. It uses almost no CPU. With kern.threads.virtual_cpu=2 or kern.threads.virtual_cpu=4 and growing scanner load, the CPU load grows exponentially. The initial fork() seems not to be the problem. It happens in the foreground mode (without any fork call) too, but only if there is some amount of scanner load. Setting maxthreads in clamd.conf seems to make the situation even worse. libthr and libc_r work without any problems and ktrace here doesn't show any fork() calls at all. I wonder if something else could get libpthread spinning on kse activation stuff. I still think something is wrong here. Martin Martin Blapp, ------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E ------------------------------------------------------------------