From owner-freebsd-current@FreeBSD.ORG Wed Feb 23 20:20:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE0E7106566B; Wed, 23 Feb 2011 20:20:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7D53F8FC1C; Wed, 23 Feb 2011 20:20:28 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 29C8846B03; Wed, 23 Feb 2011 15:20:28 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3F3768A009; Wed, 23 Feb 2011 15:20:27 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 23 Feb 2011 15:17:06 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <20110222223314.GA72748@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201102231517.06962.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 23 Feb 2011 15:20:27 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=0.5 required=4.2 tests=BAYES_00,MAY_BE_FORGED, RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Ivan Voras Subject: Re: Wow... (<-- blown away at performance) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Feb 2011 20:20:28 -0000 On Wednesday, February 23, 2011 2:11:35 pm Ivan Voras wrote: > On 22/02/2011 23:33, Alexander Best wrote: > > >>>>> Also, it looks like npviewer.bin still hangs to resources on until > >>>>> Firefox closes (or I kill it :)..), so something still needs to be > >>>>> resolved there, but that isn't a regression (it's acted that way for > >>>>> ages), and shouldn't be too hard to do. > > While on the subject - any ideas why npviewer.bin is present as so many > processes? They all appear to have some identical properties, most > curiously their memory usage, so shouldn't they be threads? Threads in Linux processes show up as individual processes. -- John Baldwin