From owner-freebsd-java Thu Jun 6 15:48:15 2002 Delivered-To: freebsd-java@freebsd.org Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by hub.freebsd.org (Postfix) with ESMTP id DEFCC37B405 for ; Thu, 6 Jun 2002 15:48:12 -0700 (PDT) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17G634-0000nJ-00; Thu, 06 Jun 2002 15:48:06 -0700 Date: Thu, 6 Jun 2002 15:48:06 -0700 To: "Robert F. Ross" Cc: Jan Grant , freebsd-java@freebsd.org, Bill Huey Subject: Re: green vs. native threads Message-ID: <20020606224806.GA3049@gnuppy.monkey.org> References: <20020606221014.GA2514@gnuppy.monkey.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: Bill Huey Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jun 06, 2002 at 03:44:51PM -0700, Robert F. Ross wrote: > Ah. The process appears to actually function and do everything it's > supposed to, so I don't think it's the SIGSEGV issue (I'm still not sure > what the libc_r signal debugging stuff is, I don't debug stuff on freebsd > often). The most likely thing from the replies I've seen is that the > pthread library is busywaiting during select() or something. It does > everything it's supposed to but tends to burn 100% cpu even when it > shouldn't need to. How many threads are you running ? I can't think of anything in libc_r that would suck so much CPU time other than it bogging down from trying to manage a zillion threads. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message