From owner-freebsd-java Wed Mar 15 15: 6:44 2000 Delivered-To: freebsd-java@freebsd.org Received: from beta.nova.org (beta.nova.org [209.31.144.41]) by hub.freebsd.org (Postfix) with ESMTP id 12B5F37BD7E for ; Wed, 15 Mar 2000 15:06:30 -0800 (PST) (envelope-from bsletten@nova.org) Received: from fcac.org (members.fcac.org [209.31.144.35]) by beta.nova.org (8.9.1/8.9.1) with ESMTP id SAA07493 for ; Wed, 15 Mar 2000 18:06:28 -0500 (EST) Received: from localhost by fcac.org (8.8.8+Sun/SMI-SVR4) id SAA17034; Wed, 15 Mar 2000 18:06:26 -0500 (EST) Date: Wed, 15 Mar 2000 18:06:25 -0500 (EST) From: Brian Sletten To: freebsd-java@freebsd.org Subject: Green Thread Starvation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running into a problem where it seems very easy to starve out the AWT Event thread using Blackdown's JVM under Linux emulation. It takes very little to make the Swing app completely unusable if there are a few threads going on at the same time. Is this combination just retardedly bad for threading? The same code seems to work dramatically better under a real Linux machine. I haven't tried it with only green threads on the same box. Has anyone else done anything thread-heavy with the combination of Linux emulation and Blackdown's JVM? (particularly with a UI) I haven't noticed the problems as dramatically doing multi-threaded server code on the same box. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message