The biggest difference is that the CLR supports you to specify stack allocation for user-defined types. With the JVM, this only happens for primitives or as an optimisation, typically when escape analysis is enabled.
The CLR is also able to better adjust the OS memory it uses in response to heap used by your program. It's not all sunshine and rainbows though, there's a performance cost for this extra flexibility. On 11 November 2010 14:08, Carl Jokl <[email protected]> wrote: > I have tried to read up a bit on this subject but have not found any > detailed technical comparisons between the Java Virtual Machine and > the .Net CLR. They both seem to operate in very similar ways but have > some differences in the bytecode. I would be interested in learning > more about how they compare. I know the CLR supports unsigned > primitive types were the JVM does not. > > I would have expected that there would be more comparisons also of the > performance of the two but I hear conflicting stories about whether > the JVM or the CLR performs faster as a virtual machine. > > There are also potential differences in the memory models of the two. > > I wonder if anyone can shed any light on this? > > -- > 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]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- Kevin Wright mail / gtalk / msn : [email protected] pulse / skype: kev.lee.wright twitter: @thecoda -- 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.
