Hi folks,
I've just installed two versions of the JDK1.2.2 for linux: Sun's RC2, and
Blackdown's RC3. I am experiencing the wierdest behavior I have ever seen
for a JDK.
Here is what I am *used* to seeing. We run Java all day long on Solaris
Sparc and x86 and Windows NT. With green threads, things are slow as hell,
and the processors are kept very busy, even when the program is idle. With
native threads, everything zips along nicely.
Here is what I see with Linux. I am running on a freshly installed RedHat
6.1 machine. With either JDK, running in native threads is absolutely
crippling. There seems to be a serparate JDK process ID for each running
thread, or otherwise something is casuing it to fork 15 times. Of these
threads four or five of them just hammer the CPU, leaving the whole
machine at a crawl. Actual performance of our Java GUI isn't too bad, but
it's no where near where it should be.
Switch to green threads. With Sun's JDK it's like lightning. Processor
utilization is practically nill, and the GUI is extremely responsive. With
Blackdown's JDK, processor utilization is also very low, but GUI
responsiveness is very low as well.
I have looked through all the FAQs I could find, tried the various
combinations of env variables.
Anyone else experienced this behavior? Really odd. Any fixes, work
arounds, or do I just hope something miraculous happens between the
release candidates and the release?
Thanks!
-Dan Stux
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
