3 ms·
Were those simple benchmarks running on Mono? .Net is certainly going open-source, but it hasn't arrived yet. It might be worth rerunning those benchmarks once
by chadzawistowski 12y ago
Were those simple benchmarks running on Mono? .Net is certainly going open-source, but it hasn't arrived yet. It might be worth rerunning those benchmarks once .Net proper is available for *nix.
- saosebastiao 12y agoYes they were on the latest version of Mono, which in my experience outside of web programming is just as fast as the JVM. I think the gap has more to do with the libraries than the VM, but I'd be willing to wait it out to see. I'm not migrating soon anyway...although it would be nice to know how far out it is.
- Hakeashar 12y agoLately I checked the Perlin noise performance test that was linked to on reddit (http://www.reddit.com/r/programming/comments/31mzu1/go_vs_rust_vs_d_vs_crystal_etc_perlin_noise/ http://www.reddit.com/r/programming/comments/31mzu1/go_vs_ru...). Summary: Benchmark: C# (Mono) - 1052.041381 ms, Java - 597.9874 ms My machine: C# (Windows) - ~475 ms, Java - ~552 ms Even considering that Mono is using maximum precision available (so instead of floats it's using doubles), when I swapped all floats to doubles it still ran in ~525 ms on my box. So while Mono might be 'getting there', sometimes it's still lagging behind. It's just something to keep in mind :)
- latkin 12y ago+1 on this - getting ASP.NET working really well on Linux/Mac, with first-party framework and VM, is the main goal for all of the in-flight .NET Core CLR open source stuff. That + console apps are literally all that's going to be supported, at least initially. Microsoft cares a lot about making this good.