JVM sloooowww on solaris/linux

Hello all,

I'm wondering if anyone has any insight on this:

Why is Sun's JVM for Solaris and Linux so much slower than their JVM for Windows? I'm running Forte For Java, v3.0 on the same system (PIII 600/640 megs ram). I've done this with JDK1.3.1 and JDK1.4b2.. all results are the same.

When I run FFJ in Windows, it's very fast -- a pleasure to use. When I reboot and run FFJ in Linux (on the same system), it's painfully slow. Scrolling the source screen is horrible, it locks for several moments every 2 or 3 minutes, and tabbing between workspaces is aweful.

I've seen the same results on an UltraSparc 10 with Solaris 8.

Why can Sun create such a fast VM for Windows, but not Solaris or Linux?

[761 byte] By [desau13] at [2007-9-26 9:27:31]
# 1
Have you tried increasing the max heap space on those machines?
jschell at 2007-7-1 20:49:32 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 2
Maybe it is because of the thread.As i know the linux kernel doesnot support thread.Regards!
IPOz at 2007-7-1 20:49:32 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 3

Linux isn't threaded in the traditional definition of the word, instead is uses multiple 'processes'. It works out to be the same performance (with a little overhead saving). The results are the same on Solaris.. which is muti-threaded. It just seems that Sun's VM for Unix and Unix-like systems sucks.

desau13 at 2007-7-1 20:49:32 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 4
My experience is that the JVM itself is plety fast, it is Swing on Unix that tends to have problems. Are the consoles local?
cmccorvey at 2007-7-1 20:49:32 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 5
Yes, local.But, yes.. it's heavy in Swing.Perhaps that's it.
desau13 at 2007-7-1 20:49:32 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 6

Linux on an X86 should be about as fast as that same machine running windows. UltraSparc chips.. and other register rich chips have extra overhead of calculating register allocation on the fly... where X86 chips don't have any registers...(ha ha).. So it doesn't take as much time to JIT the code. At least that's been my experience. Any comments on this?

SpinozaQ at 2007-7-1 20:49:32 > top of Java-index,Java HotSpot Virtual Machine,Specifications...