4 ms·
> I heard so many times that JVM is much better than CLR, especially in the JIT area (Hotspot?). I wouldn't disagree with this (I work at Oracle on VM research
by chrisseaton 9y ago
> I heard so many times that JVM is much better than CLR, especially in the JIT area (Hotspot?).
I wouldn't disagree with this (I work at Oracle on VM research), but I've been told by other people that Microsoft or at least the .NET just generally prefer a simpler approach, without profiling, dynamic compilation, deoptimisation, and other complexity the approach used by the JVM brings. It's much more what-you-see-is-what-you-get from their JIT, rather than the mind-binding things the JVM manages to do with some code, and maybe that makes life easier for their use cases.
I'm not sure they want to add the same kind of complexity that the JVM has, even if it did bring them some better performance. But as I say that's second hand conversations.
- sreque 9y agoI definitely agree with this stance, and would say that languages like C# and golang have a weaker runtime but try to make up for it in other ways, often surpassing Java in certain areas. For instance, both languages have stack-allocated types to help stress the GC less. C# also has a much better native interop story than Java, as well as the unsafe keyword. At the end of the day, if you want amazing performance in Java, you have to write C-like code in Java, and that often involves things like managing your own offheap memory, sticking with arrays of numbers, etc. Java's biggest areas for improvement in the performance arena are going to come allowing for stack-allocated types, fully-continugous arrays, less overhead when calling native code, and providing official APIs for the other things you can currently do with sun.misc.Unsafe.
- naasking 9y agoThe .NET runtime is weaker on the JIT side, but the lack of type erasure on generics is very complicated all on it's own. Java doesn't have to deal with this. In fact, .NET is the only VM I know of with this feature. Fortunately, it permits a lot of interesting manual optimizations you can't easily express when runtime types aren't available.
- seanmcdirmid 9y agoThe lack of erasure is a huge usability win (types don’t disappear at run time), as well as a performance win (I’ve been able to do great things with C# generics + value types). I also like the way it naturally deals with static fields (useful for factory routines).
- throwaway010317 9y agoI use C# in my day job and try to learn as much as I can about cool ways to use its type system. Genuinely curious to see some examples if you're able to point me in the right direction? > I’ve been able to do great things with C# generics + value types
- naasking 9y agoYou can see a few tricks in my project here: https://github.com/naasking/Dynamics.NET https://github.com/naasking/Dynamics.NET You can use static classes to cache information about types. That project caches delegates to perform deep copies, to invoke constructors, to check for deep immutability, and whether a type can contain any cycles. This is all done structurally via reflection, but the results are executed only once and cached in static fields by exploiting runtime types. The cached delegate trick can be used whenever you need to some efficient dynamic dispatching. I use it here [1] in another project to cache the Dapper methods that would be invoked so I can easily compose smaller queries into larger ones that return very complicated objects. A more complicated example would be the fastest immutable dictionary available for .NET in my Sasa library [2]. Generic methods and types defined on structs are JITted separately, so the dispatching overhead is low. I exploit this to create a very efficient hash array mapped trie. [1] https://github.com/naasking/Dapper.Compose/blob/master/Dapper.Compose/Query.cs#L90 https://github.com/naasking/Dapper.Compose/blob/master/Dappe... [2] https://sourceforge.net/p/sasa/code/ci/default/tree/Sasa.Collections/Trie.cs https://sourceforge.net/p/sasa/code/ci/default/tree/Sasa.Col...
- pron 9y agoI think it's a huge loss. Generic type erasure is the main thing that makes simple polyglot interop and code-reuse on the JVM possible. Even things like Python become clunky on .NET because of runtime generics. I gladly give up on the tiny usability gain in exchange for having a rich language ecosystem. Value types are a different matter, and they are now being added to Java as well. Specialized generics over value types are different from specialized generics for reference types, because they are always invariant.
- matthewwarren 9y ago> but I've been told by other people that Microsoft or at least the .NET just generally prefer a simpler approach, without profiling, dynamic compilation, deoptimisation, and other complexity the approach used by the JVM brings. It's much more what-you-see-is-what-you-get from their JIT, rather than the mind-binding things the JVM manages to do with some code, and maybe that makes life easier for their use cases. Interesting, it's clear after a bit of research that this is the case (i.e. .NET JIT simpler that Hotspot), but it had never occurred to me that it was a conscious decision I'd always thought that the .NET was just playing catch-up and/or didn't need to do all the things that Hotspot does. (for instance .NET has value types or 'stucts' so some optimisations are not needed because the programmer can just use them instead of classes, if they need the perf boost)
- sillypuddy 9y agoIt has been a deliberate decision. The Book of the Runtime documentation states "The goal of the CLR is to make programming easy" and acknowledges there are faster alternatives out there. When I have asked insiders why there isn't a bigger focus on performance, the response is essentially that if performance is really important you should use C++.
- matthewwarren 9y ago> The Book of the Runtime documentation states "The goal of the CLR is to make programming easy" In case anyone else is interested, that quote comes from https://github.com/dotnet/coreclr/blob/master/Documentation/botr/intro-to-clr.md#the-primary-goal-of-the-clr https://github.com/dotnet/coreclr/blob/master/Documentation/...
- benaadams 9y agoAlso says > The .NET runtime supports a wide variety of high performance applications. As such, performance is a key design element for every change. https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/performance-guidelines.md https://github.com/dotnet/coreclr/blob/master/Documentation/...
- 9y ago
- mehrdadn 9y ago>> I heard so many times that JVM is much better than CLR, especially in the JIT area (Hotspot?). > I wouldn't disagree with this I would wholeheartedly disagree with this though. There's not even any way to write, say, a generic class (even one as simple as ArrayList<T>) and then let the user instantiate it with a primitive type like <int> in Java. To use generics in Java is to pay the speed penalty of an indirection for every single primitive type on top of the extra per-object bytes of space overhead. There's just no way Java is going to fix these problems without massive breaking changes in the type system or an extremely in-depth & expensive form of static analysis unlike anything I've seen in any real-world compiler.
- chrisseaton 9y agoYou're not disagreeing with me, because we're talking about different things! You're talking about Java, the language, I'm talking about the JVM, really HotSpot, really C2 actually, the implementation and the techniques it uses, whatever the language is, compared to the techniques that the .NET CLR uses. The points you bring up are interesting though, because some of these complexities (which HotSpot isn't responsible for or in a position to change!) are as someone else has said, probably partly what has motivated the extra work in C2 compared to the .NET CLR JIT. > To use generics in Java is to pay the speed penalty of an indirection for every single element on top of the extra per-object bytes of space overhead. And this is just false - the extra indirection only applies for elements that are boxed primitives, not 'every single element'. There is no extra indirection for things that are references anyway.
- mehrdadn 9y ago> You're not disagreeing with me, because we're talking about different things! You're talking about Java, the language, I'm talking about the JVM, really HotSpot, really C2 actually, the implementation and the techniques it uses, whatever the language is, compared to the techniques that the .NET CLR uses. No, we are disagreeing. I'm talking about how repercussions of decisions in the language affect the implementation. My comment was not at all limited to just the language itself. If you read my comment, you notice I mentioned fixing these issues would require changes in either the type system or an "expensive form of static analysis unlike anything I've seen in any real-world compiler". Because when the language dictates that there must be an indirection, the implementation can only remove it when it can prove that doing so would be transparent to the code, which is impossible to do in general and extremely difficult in practice. This is neither just about the language nor just about the implementation; it's about the consequences of language decisions in the implementation. > the extra indirection only applies for elements that are boxed primitives Yes, I just assumed since I had already mentioned primitives it was clear that I'm talking about the use of primitives in generics. But I'll edit it in to repeat myself.
- kittiepryde 9y agoAre there standard benchmarks used to measure and compare the two approaches (jvm vs .net)?
- chrisseaton 9y agoIt's crazy but I'm not really aware of any good benchmarks, at least in the research community. But you can show the differences qualitatively, in that the .NET simply doesn't have large swathes of optimisations which I think are considered pretty fundamental in the JVM such as escape analysis.
- benaadams 9y agoPinch of salt with all benchmarks, but "The Computer Language Benchmarks Game"? http://benchmarksgame.alioth.debian.org/u64q/csharp.html http://benchmarksgame.alioth.debian.org/u64q/csharp.html .NET does better in most of them, but falls down vs Java on Regex and k-nucleotide
- deleted 9y ago[deleted]