6 ms·
Most of it is generic enough to be applicable to anything that calls itself a JVM since it's required by spec. For instance, everything bytecodes, what a class
by pvg 8y ago
Most of it is generic enough to be applicable to anything that calls itself a JVM since it's required by spec. For instance, everything bytecodes, what a class file looks like, how dynamic linking works, etc.
- pjmlp 8y agoAnyone that has had to track down issues between Sun(Oracle) and IBM caused by GC or JIT differences, will have a different opinion. I surely have been there a few times.
- pvg 8y agoWhy would you have a different opinion? This post is almost entirely not about stuff like that. If anything, the other linked thing in this thread 'JVM Anatomy' and this post should meet somewhere and agree to swap titles.
- pjmlp 8y agoBecause those things are left unspecified and they matter specially under heavy load. A JEE server might scale differently depending under which JVM it is running. The GC algorithm chosen by the implementation might lead to higher pauses in another JVM. The beautiful auto-vectorized code in one JVM might run like molasses in another JVM. One JVM might lack tiered compilation, thus increasing the saw shape pauses when it comes to JIT a specific method. Finally, the spec doesn't state how threads are executed, so they can be implemented as green or red threads, and certainly the code won't run the same way.