> Hotspot is *not* a traditional JIT compiler. While that was true in > the early days of HotSpot (many years ago) today it does lots of > advanced realtime prediction and analysis.
Well I think that's kind of the point, nobody is dissing the performance of hotspot, they are (in the white paper I liked to anyway) arguing that sometimes the simpler approach yields a better price/performance outcome. This would be the case for non-server stuff for instance. > I think they just mention Java's VM because it's the one most people > are familiar with. If the CLR was more commonly used they would have > mentioned that instead. :) More commonly used? Nah it probably has more to do with the fact that a tracing JIT has more in common with how the JVM first interprets and then JIT's hotspots, whereas the CLR always JIT's the whole thing. /Casper --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
