So when would be an exe cache in the hotspot?
It’s not too difficult, just one interface and SHA 2 hashing. Hotspot is able to do an on stack replacement anyway so it might be included in 1.6 without problems. I really wonder why JVM didn’t posted a window with text “Program xxxxx is inicializing: testing xxxx , loading fonts, testing xxxx. transfering control to program”
Then on exit it could post a some window with meaningless statistics.
You can get some “meaningless statistics” out of the current hotspot compiler.
-XX:+PrintCompilation for example will show you what methods are being compiled to native code.
There are other useful bits of information that you can get, some of them require a debug build of hotspot though.
[quote]I still find it ridiculous how slow Java2D is on the Mac. I’m getting a max of 1200 FPS on my crap 2.4GHz Dell and only about 150 FPS on my 1GHz eMac.
[/quote]
If you can, try running with Java 1.3 on the Mac. It has a different graphics pipeline.
In 1.4 on the Mac there is NO hardware acceleration of graphics. the reason being that the core graphics routines in the OS are being optimized to use hardware acceleration for OS X 10.4 (Tiger) as I understand it. Also the apple Java guys figured on taking advantage of the openGL pipeline in Java 5. So they conserved their efforts to areas where it would pay off most… and that basically meant a delay in getting accelerated graphics for java on the Mac. It does suck, but hopefully it will pay off when 10.4 is released with Java 5.