2 ms·
Don't get me wrong I'm sure native C# is plenty fast and within acceptable speed range. It it were me, native code would be used at a last resort strategy. But
by p0nce 6y ago
Don't get me wrong I'm sure native C# is plenty fast and within acceptable speed range. It it were me, native code would be used at a last resort strategy.
But perusing https://benchmarksgame-team.pages.debian.net/ https://benchmarksgame-team.pages.debian.net/ is still seems C# takes much more memory? It's strange as such benchmark don't expose much change between .net and .net aot
- igouy 6y agohttps://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/csharpcore-csharpaot.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/... Maybe we're doing something wrong? Don't know what.
- p0nce 6y agoLooks like measuring the same thing twice.
- igouy 6y agoOnce with /usr/bin/dotnet build -c Release --no-restore -r ubuntu-x64 and once with /usr/bin/dotnet publish -c Release --no-restore -r ubuntu-x64 --no-self-contained What should the second do for aot ?
- igouy 6y ago"Applications that have small amounts of code will likely not experience a significant improvement from enabling ReadyToRun, as the .NET runtime libraries have already been precompiled with ReadyToRun." https://docs.microsoft.com/en-us/dotnet/core/deploying/ready-to-run https://docs.microsoft.com/en-us/dotnet/core/deploying/ready...