2 ms·
I haven't used the JVM in a long time, but .NET Core starts up pretty damn quick from cold IL. I believe the tiered compilation approach has something to do wit
by bob1029 6y ago
I haven't used the JVM in a long time, but .NET Core starts up pretty damn quick from cold IL. I believe the tiered compilation approach has something to do with the fast startup + insane web benchmarks.
- amelius 6y agoDid Microsoft Research publish papers on how the dotnet virtual machine pulls this off?
- whizzter 6y agoThe reason for benchmark performance isn't related to the JIT only but rather of .NET being more "pragmatic" with memory slices(usable with stack allocs,mmap), value types and in/out/ref passing. These little things together makes the .NET code run with far less GC pressure and more cache locality like C++ code without making the code non-idiomatic (Yes, A JVM system can be written like QuestDB to achieve similar perf but it won't be idiomatic Java code). Then the Kestrel server + new ASP.NET Core runtimes takes advantage of it (for example the new JSON parsing API's are built to directly consume byte memory w/o sacrificing too much extensibility).
- pedrow 6y ago.NET has a Global Assembly Cache[0] which I think (please correct if I'm wrong) is used to pre-compile the system frameworks and so makes startup faster. [0]: https://docs.microsoft.com/en-us/dotnet/framework/app-domains/gac https://docs.microsoft.com/en-us/dotnet/framework/app-domain...
- mythz 6y agoOnly the legacy Windows .NET Framework has a Global Assembly Cache which doesn't exist in .NET Core. Although the cross-platform .NET Core runtime does get pre-installed with a number of default Microsoft packages in its local NuGet package cache.
- fctorial 6y agoWhy doesn't jvm cache the jit compilation results?