Startup times are through the floor on Edge

Unity Engine
1

Project built with Unity 5.3.8, startup time on Edge 12 secs
Project built with Unity 5.6.3, startup time on Edge 2 mins 24 secs

Project built with Unity 5.3.8, startup time on Chrome 8 secs
Project built with Unity 5.6.3, startup time on Chrome 16 secs

Nightmare.

1 Like
2

seems very strange. Are you comparing the same type of build (non-development) ?

3

Yes these are “launch” ready builds. The only difference being one is already live, Unity 5.3.8, and is on our live server and the new one, Unity 5.6.3 is on our Stage server. I can see in the console though that the load time is barely affected as all the data comes from the same cdn. It’s the “initialising” phase that takes over 2 minutes, the download and decompression takes a few seconds.

I’ve just found out too that anti-aliasing is broken in Edge Unity 5.5+ so it’s not really usable anyway.

[Anti-aliasing issue fixed by 5.6.3p4 patch]

4

could you, perhaps privately, share links to the builds?

re. AA, see my reply on other thread.

5

Done

6

Setting the “Content-encoding” header on the files to “br” seems to have decreased the startup time to a more reasonable 18 secs

7

Unfortunately although that fixes it for Edge it then breaks it for Chrome, so in Chrome I now get this error

Failed to load resource: net::ERR_CONTENT_DECODING_FAILED for each .unityweb file

8

Poking around a bit more it seems that Cloudfront doesn’t support brotli so the only option is to use gzip and set the Content-Encoding headers to gzip, that appears to load at a suitable speed on all browsers