Although if I understood this correctly, these performance improvements will only take effect if you compile using .Net Core 2.0 and run using .Net Core 2.0 runtime? I did not realize .Net Core had diverged this much from .Net Framework.
Performance Improvements in .NET Core
81–90 of 94 posts
Re: Performance Improvements in .NET Core
#82What's up with the memory consumption of C# .Net Core? It looks like it has dethroned Java as the memory bloat champion. http://benchmarksgame.alioth.debian.org/u64q/csharp.html
Re: Performance Improvements in .NET Core
#83Earlier quoted context omitted.
Actually the instructions for Debian are the best: download the tarball, adjust $PATH and go: https://www.microsoft.com/net/core#linuxdebian But I went "ubuntu" route and bailed, looking for a simple tarball.
Why is the Ubuntu route too difficult?
If you don't like it you can install the same debian tarball on ubuntu.
Re: Performance Improvements in .NET Core
#84Is there something like Heroku but for dotnet core apps? I'd like to play a bit with it but it should be as easy as pushing to a repo to deploy and run.
Why do you need to push to a repo to deploy/run? If you want to play just create a project and run it locally.
What would be the easiest way to run on macOS?
Re: Performance Improvements in .NET Core
#85This is great and a very detailed report as well! Although if I understood this correctly, these performance improvements will only take effect if you compile using .Net Core 2.0 and run using .Net Core 2.0 runtime? I did not realize .Net Core had diverged this much from .Net Framework.
Yeah me too.
On the flip side I consider it a healthy sign for the project as a whole and especially as an open-source undertaking.
Re: Performance Improvements in .NET Core
#86What's up with the memory consumption of C# .Net Core? It looks like it has dethroned Java as the memory bloat champion. http://benchmarksgame.alioth.debian.org/u64q/csharp.html
I played around with the binary-tree code. It's definitely because of Task (disabling the >= 17 heuristic doubles the memory usage). This should come way down with .Net Core 2.0 and ValueTask.
Re: Performance Improvements in .NET Core
#87Earlier quoted context omitted.
Are any of those discussions around better way to write the benchmarks public? From a very quick look, something like http://benchmarksgame.alioth.debian.org/u64q/program.php?tes... looks like a direct port from a C program, rather than idiomatic C#.
Some of them seem to have some rules [1] like: > Please don't implement your own custom "arena" or "memory pool" or "free list" - they will not be accepted. > ... > We ask that contributed programs not only give the correct result, but also use the same algorithm to calculate that result. So there might not be too much room to improve. There could be some room to improve for things like "custom ... memory pool" since…
Re: Performance Improvements in .NET Core
#88Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
Re: Performance Improvements in .NET Core
#89Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
https://www.hanselman.com/blog/TryingNETCoreOnLinuxWithJustA...
Re: Performance Improvements in .NET Core
#90Whenever I look at drastic improvements in performance, I remember that a while ago I managed to speed up a custom parser at work, by about 30x. When I emailed my colleagues, I just said "You may consider this to be work of a genius. Or you may think I was stupid when writing the original implementation. I'll let you pick the narrative that you fancy." Interpretations are fun when there's a baseline :-)