Game Development

Unity Benchmark report approves WebAssembly load times and performance in popular web browsers

2 min read

Unity has released a benchmarking report after two years since the last Unity Benchmark report comparing the performance and load times of WebAssembly with asm.js. They have compared the performance of Unity WebGL in four major web browsers: Firefox 61, Chrome 70, Safari 11.1.2 and Edge 17.  Last month, Unity officially announced that it is finally making the switch to WebAssembly as their output format for the Unity WebGL build target.

Note: All images and graphs are taken from the Unity Blog.

For running the tests, the team rebuilt the Benchmark project with Unity 2018.2.5f1 using the following Unity WebGL Player Settings:

Here are the findings from the report.

Criteria 1: Total amount of time taken to get to the main screen for both WebAssembly and asm.js.

Findings:

  • Firefox is comparatively fast to load on both Windows and macOS
  • Chrome and Edge load faster when using WebAssembly
  • All browsers, except Safari, load faster with WebAssembly compared to asm.js.

Criteria 2: In-Depth Load Times for WebAssembly-only.

The team compared four factors:

  • WebAssembly compilation and instantiation.
  • Unity engine initialization and first scene load.
  • Time it takes to render first frame.
  • Time it takes to load and have a stable frame-rate.

Findings:

  • Firefox is the fastest overall on both Windows and Mac
  • Edge compiles Wasm quickly (even faster than Firefox) but is slower in Unity engine initialization.

Criteria 3: Performance and Load times for Real-World Projects

Real-world projects result in larger builds which impact the end-user’s experience. Here is an overview of total scores using WebAssembly and asm.js

Findings:

  • All browsers perform better when using WebAssembly
  • On Windows, all browsers perform similarly
  • On macOS, Firefox outperforms all other browsers.
  • Safari is the browser that benefits the most by WebAssembly since it doesn’t support asm.js optimizations.

Conclusion

The report findings conclude that modern browsers load faster and perform better thanks to WebAssembly. It also provides more consistent user experience as compared to asm.js.

Read more about the findings on the Unity Blog.

Read Next

Unity releases ML-Agents toolkit v0.5 with Gym interface, new suite of learning environments.

Key Takeaways from the Unity Game Studio Report 2018.

Unity switches to WebAssembly as the output format for the Unity WebGL build target.

 

Sugandha Lahoti

Content Marketing Editor at Packt Hub. I blog about new and upcoming tech trends ranging from Data science, Web development, Programming, Cloud & Networking, IoT, Security and Game development.

Share
Published by
Sugandha Lahoti
Tags: Unity News

Recent Posts

Top life hacks for prepping for your IT certification exam

I remember deciding to pursue my first IT certification, the CompTIA A+. I had signed…

3 years ago

Learn Transformers for Natural Language Processing with Denis Rothman

Key takeaways The transformer architecture has proved to be revolutionary in outperforming the classical RNN…

3 years ago

Learning Essential Linux Commands for Navigating the Shell Effectively

Once we learn how to deploy an Ubuntu server, how to manage users, and how…

3 years ago

Clean Coding in Python with Mariano Anaya

Key-takeaways:   Clean code isn’t just a nice thing to have or a luxury in software projects; it's a necessity. If we…

3 years ago

Exploring Forms in Angular – types, benefits and differences   

While developing a web application, or setting dynamic pages and meta tags we need to deal with…

3 years ago

Gain Practical Expertise with the Latest Edition of Software Architecture with C# 9 and .NET 5

Software architecture is one of the most discussed topics in the software industry today, and…

3 years ago