Slashdot Mirror
Unity Benchmarks Browser WebGL Performance (unity3d.com)
An anonymous reader writes: Jonas Echterhoff from Unity has posted the latest Unity WebGL benchmark results on the Unity blog. He writes, "A bit over a year ago, we released a blog post with performance benchmarks for Unity WebGL, to compare WebGL performance in different browsers. We figured it was time to revisit those benchmarks to see how the numbers have changed. Microsoft has since released Windows 10 with their new Edge browser (which supports asm.js and is now enabling it by default) – so we were interested to see how that competes. Also, we have an experimental build of Unity using Shared Array Buffers to run multithreaded code, and we wanted to see what kind of performance gains to expect. So we tested this in a nightly build of Firefox with Shared Array Buffer support." The benchmark concludes that Firefox 42 64-bit is the fastest, Edge takes second, and Chrome and Safari share third place.
Nothing can beat Chrome
Except for Firefox and Edge. At least Chrome ties with Safari. Third is better than fourth!
Well, the benchmarks speak a very different story. While IE is slow beyond use, Edge with asm.js actual performs pretty well, much better then Chrome.
In general, I am very happy with the direction MS is taking with Edge, and have so far found it not to be "the new IE" at all, quite to the contrary. Following open web standards, maintaining public page to track new developments (https://status.modern.ie), great performance - all of this sounds very promising to me.
Back when Epic first ported Unreal Engine to run in a browser, the only browser it really worked well in was Firefox. Now, Firefox is still the best performer for these kinds of tasks.
Now, commence with the replies explaining why Firefox is a memory hog and not worth using, but it's some kinda weird memory hog that for the past 3-4 years actually uses less memory than Chrome or any other browser.
If it only had some manner of extension or userscript support. Browsing without ad blocking feels so 90's.
Except Chrome was not number one in any benchmark. In fact, it was between IE 11 and FireFox 46 in every single benchmark.
Reading, it's neato!
Your ad here. Ask me how!
Yes, this is mostly memory related. Browsers have a tendency to either crash when parsing all the code, or to run out of memory when trying to allocate the memory for the game itself (which emscripten implements using a single big array of bytes in JavaScript). See http://docs.unity3d.com/Manual...