Production Client Side Apps not using Sun JVM?

Question

Just wondering if anyone here deploys a non-Sun JVM to client machines?
The impression I get is that everyone tends to just stick with the Sun JVM because is easily available and reliable.
However, I'm considering suggesting that our clients move to a different JVM for the performance reasons described below:
I wrote a series of performance tests to measure the time taken to repeat certain common tasks from our apps. I was surprised to find that the BEA JRockit JVM outperformed the SUn JVM by a long, long way in certain tasks, and was slower in none.
Here's a selection of (subjective) results:
Log Lines written per second - Sun 21,000 BEA 29,000
Time taken to call (100000000) methods - Sun .907s BEA .269s
Time taken to call (100000000) sync methods - Sun 17s BEA 12.4s
Time to create big byte array - Sun 125ms BEA 32ms

Answer 1

i would go for the intel/dual-proc optimisation answer for the difference.
Although 50%? Logging to files uses most time with file access. Didn't know that was optimized either. (learning new stuff every day :-)
But then again, 1 great thing about Java: write once, run anywhere (on any JVM, except for mickeysoft: they have their own neat thingie called the M$ VM, which downgrades performance by a 1000% and uses the 1.1.3 spec)
As a thumb rule: either provide the JVM of your choice to your customers and make it mandatory to use that one, or make sure that it runs with (reasonable) performance under the slowest JVM. (p.s. 99% of the users use the Sun JVM for what i've seen, so if you let your clients choose: Sun's the way to go).