Tuesday April 07, 2009
Tuesday April 07, 2009 There has been a lot of public comments about the modifications we've made to Harmony's java.util.TreeMap implementation. We've been working on it since I announced our use of the code last summer. Reliability and compatibility are our greatest concerns, and much of the last several months have been spent flushing out obscure compatibility concerns. Of course, some of the time has been spent in legal reviews for open source contributions. However, today is the day.
I am very happy to announce that after completing Sun's open source review process, along with many iterations of quality assurance and compatibility testing we are engaging the Harmony community to do as we said we would, give the modifications we made to java.util.TreeMap back to Harmony.
While the modifications made to this TreeMap meet the Java 6 specification there remains behavioral compatibility differences between the TreeMap from Harmony and the TreeMap implementation in OpenJDK. These inconsistencies are continuing to be discovered and addressed --- compatibility is very important to us! However, it appears to be important to Harmony to receive the modifications immediately. More important than spending the engineering time to deliver an implementation that is fully compatible, beyond the Java 6 specification, with Java 6 TreeMap or OpenJDK's TreeMap. Hence, we are giving these modifications to Harmony in their current form.
Last but not least, it seems its time for Tim to make his £500 donation to the Woodland Trust. I expect it would be too much to ask that it be done on behalf of the Sun Java development team :-) Either way, I expect a bit of head slapping and tree hugging in Hampshire, UK tomorrow.
I am very happy to announce that after completing Sun's open source review process, along with many iterations of quality assurance and compatibility testing we are engaging the Harmony community to do as we said we would, give the modifications we made to java.util.TreeMap back to Harmony.
While the modifications made to this TreeMap meet the Java 6 specification there remains behavioral compatibility differences between the TreeMap from Harmony and the TreeMap implementation in OpenJDK. These inconsistencies are continuing to be discovered and addressed --- compatibility is very important to us! However, it appears to be important to Harmony to receive the modifications immediately. More important than spending the engineering time to deliver an implementation that is fully compatible, beyond the Java 6 specification, with Java 6 TreeMap or OpenJDK's TreeMap. Hence, we are giving these modifications to Harmony in their current form.
Last but not least, it seems its time for Tim to make his £500 donation to the Woodland Trust. I expect it would be too much to ask that it be done on behalf of the Sun Java development team :-) Either way, I expect a bit of head slapping and tree hugging in Hampshire, UK tomorrow.
Thursday April 02, 2009 Tim Ellison of the Harmony project has attempted to discredit my blog post on Intel Nehalem. I'm quite aware of IBM's stellar performance on a "similar" platform, however I wasn't at the liberty to comment on it until a public statement from IBM was made. Now that has happened...
Congratulations to IBM J9! Your SPECjbb2005 score is impressive and I look forward to beating it shortly :-) No, seriously, you've done a great job. However, why don't you submit a SPECjvm2008 result? Actually no company besides Sun has submitted a result! Why is that? From my perspective the benchmark is being avoided because no one can beat the Sun result. If a JVM was truly the fastest on the planet it would step up and beat Sun at SPECjvm2008. Same applies for single-JVM SPECjbb2005, looking at your current results a single-JVM run IBM J9 should look good. Come on, make me eat my words.
Look for a blog about SPECjvm2008 on Nehalem in the next few days...
All of our performance optimizations for Intel's latest processor are found in the OpenJDK JVM now. Sun HotSpot JVM is open source, you can find all the source here. Sun Java 6 Updates and Performance releases are Sun's distribution of Open JDK. All performance optimizations make their way into Open JDK, HotSpot optimizations have made it into Open JDK faster than the library changes. The latest performance release will run on hs15, Open JDK runs on hs15. To say that we're not open source is simply wrong.
Sun and Open JDK take reliability and stability very seriously. It is the foundation of a vast majority of Java deployments out there today, let alone its use on the client. Spouting complaints about how slow we integrate performance optimizations into Open JDK is misleading/misguided. As for TreeMap, I have to say we're very close. Its under-review for our outbound open-source contributions. I look forward to announcing it in the weeks to come, and also look forward to Tim's £500 donation. Its slow because we are diligent about overall performance impact, and strict when it comes compatibility. SPECjbb2005 is small potatoes when considering reliability and stability.
Congratulations to IBM J9! Your SPECjbb2005 score is impressive and I look forward to beating it shortly :-) No, seriously, you've done a great job. However, why don't you submit a SPECjvm2008 result? Actually no company besides Sun has submitted a result! Why is that? From my perspective the benchmark is being avoided because no one can beat the Sun result. If a JVM was truly the fastest on the planet it would step up and beat Sun at SPECjvm2008. Same applies for single-JVM SPECjbb2005, looking at your current results a single-JVM run IBM J9 should look good. Come on, make me eat my words.
Look for a blog about SPECjvm2008 on Nehalem in the next few days...
All of our performance optimizations for Intel's latest processor are found in the OpenJDK JVM now. Sun HotSpot JVM is open source, you can find all the source here. Sun Java 6 Updates and Performance releases are Sun's distribution of Open JDK. All performance optimizations make their way into Open JDK, HotSpot optimizations have made it into Open JDK faster than the library changes. The latest performance release will run on hs15, Open JDK runs on hs15. To say that we're not open source is simply wrong.
Sun and Open JDK take reliability and stability very seriously. It is the foundation of a vast majority of Java deployments out there today, let alone its use on the client. Spouting complaints about how slow we integrate performance optimizations into Open JDK is misleading/misguided. As for TreeMap, I have to say we're very close. Its under-review for our outbound open-source contributions. I look forward to announcing it in the weeks to come, and also look forward to Tim's £500 donation. Its slow because we are diligent about overall performance impact, and strict when it comes compatibility. SPECjbb2005 is small potatoes when considering reliability and stability.