From owner-freebsd-hackers@FreeBSD.ORG Tue May 25 19:05:42 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DBD31065672 for ; Tue, 25 May 2010 19:05:42 +0000 (UTC) (envelope-from george@m5p.com) Received: from mailhost.m5p.com (unknown [IPv6:2001:418:3fd::3]) by mx1.freebsd.org (Postfix) with ESMTP id D2BFD8FC2C for ; Tue, 25 May 2010 19:05:41 +0000 (UTC) Received: from m5p.com (wireless.m5p.com [IPv6:2001:418:3fd::f1]) by mailhost.m5p.com (8.14.3/8.14.3) with ESMTP id o4PJ5ZUN084543 for ; Tue, 25 May 2010 15:05:40 -0400 (EDT) (envelope-from george@m5p.com) Received: (from george@localhost) by m5p.com (8.14.4/8.13.7/Submit) id o4PJ5ZnF065366; Tue, 25 May 2010 15:05:35 -0400 (EDT) Date: Tue, 25 May 2010 15:05:35 -0400 (EDT) Message-Id: <201005251905.o4PJ5ZnF065366@m5p.com> From: george+freebsd@m5p.com To: freebsd-hackers@freebsd.org X-Spam-Score: 0.63 () AWL,BAYES_00,FH_DATE_PAST_20XX,NO_RELAYS X-Scanned-By: MIMEDefang 2.64 on IPv6:2001:418:3fd::f7 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mailhost.m5p.com [IPv6:2001:418:3fd::f7]); Tue, 25 May 2010 15:05:40 -0400 (EDT) Subject: Firefox startup impacted by distributed.net client X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2010 19:05:42 -0000 OS: FreeBSD post 8.0-RELEASE Firefox: 3.6 Distributed.net client: v2.9103 and later When the distributed.net application is not running, Firefox will start up on my box in less than two seconds. But with the distributed.net application running, the firefox startup slows down painfully, taking no less than 20 seconds, and in extreme cases up to 90 seconds (out of which it takes 50 seconds for anything to appear on the screen at all). Once firefox is started, it runs very responsively. distributed.net application is 100% CPU bound, It takes a chunk of memory, but it runs at "nice 20" level. Between firefox and distributed.net, my system still uses 0% of its swap space according to swapinfo. During the startup period, top reports that firefox-bin is consuming an increasing amount of memory and spending a lot of time in "ucond" state. At a guess, something about the way firefox requests memory causes it to block for some period of time before it can do anything else. Has anyone else experienced this? How should I go about analyzing it? Thanks for your help. -- George Mitchell