Unity 2018 - WebGL lost 10 seconds to init on Chrome

Hello everyone,

My project build with WebGL, compression with Gzip and linker taget with asm.js. It is run perfect on Firefox with 1 second to init game. But on Chrome, my game lost 10 seconds to init. Is there a way to reduce boot time on Chrome?

Thank all.

My game link: http://res.12fun.net/Unity/12fun/index.html

 

Hi, @Marco-Trivellato

I tried build with WebAssembly, Unity init about 6 seconds.
link build webassembly : https://res.12fun.net/Unity/12fun-webassembly/index.html

My project build with Unity 2018.1.0f2
Brower: Google Chrome(64 bit) ver 67.0.3396.62
My Computer:

 

It's the same for me and it's like that since a long time.
The loading is so fast in firefox compared to chrome.

 

+1,
for above URL,
Safari, FF is pretty much fast like a few sec.
but on Chrome it takes 10+ sec.

Same for my game build too.

 

+1
Same for my game build too.

 

Chome has always been slow to initialize, even for wasm. The question is, are they ever going to do anything about their abysmal loading time?

 

Does anybody know why Chrome's performance so different than Firefox?

 

I suspect a few reasons, the biggest simply being Mozilla invented asm.js (which is also the foundation of wasm) and the compiler (emscripten) Unity uses for the webgl platform. You could say Mozilla has a head start.

Harder to prove (more on the hand waving side), I think historically Google has tended to favor more of a JIT style compilation over AOT. That philosophy may or may not be the right approach for the web "in general" (a separate discussion), but I think it has proven not so effective for the types of web applications Unity produces. I bet even in this "wasm world" we now live in that Mozilla's wasm compilation stack is still non-trivially better than Google's due to their previous experience with AOT compilation.

 

am sorry..... am so sorry.....
but....
you piss me off asking for webGL is slow at loading !!!!!!!
YES IT IS !!!!!!! AND NOW WHAT ?????
when you spend hours calculating lightmaps, reflmaps, pizzamaps....
what is the problem with 45sec loading of your 3D scene ????????????????????????????

there is much more important on webGL limts than the 'starting time' !!!!
think about rendertextextures !!!!
when you first played assassin's creed, didn't it take 2 minutes to load the level ?
and did you suicide in the meanwhile ?

3D is HEAVY !!!!!!!!!!
bear the burden when it's worth it !

 

WebAssembly in Chrome is not enabled by default...Experimental...
chrome://flags/#enable-webassembly
chrome://flags/#enable-webassembly-streaming

Enabling these and using the big blue "Restart" button after enabling them helps.
My almost empty project with just UI, 3 cubes and some colliders loaded up in 2 ~ 3 seconds on firefox. Chrome was about the same after enabling those experimental flags.

 

Chrome version 67.0.3396.99 I still had to enable it myself.

If I leave it on "Default" instead of "Enabled" Chrome takes longer to load and will give this message:
[Unity Cache] WebAssembly module ‘/Build/Build.wasm.code.unityweb' not stored in the indexedDB cache due to the error: DataCloneError: Failed to execute 'put' on 'IDBObjectStore': #<Module> could not be cloned.

 

Safe to ignore but if I enable both those flags mentioned before, chrome does load faster, without that error message.
Leaving the flags Default it takes longer to load than when it is enabled and getting that message.

So I am uncertain now why enabling it explicitly makes it load faster than when set to default.

 

There's also an #enable-webassembly-baseline flag in the pre-release versions (not entirely sure which Chrome channels have them, Canary definitely) that uses the new 'Liftoff' compiler, bringing initial non-cached startup times closer to that of Firefox's.