The time to "trying..." is general startup time, and the time after that and until the native-wasm method says "succeeded" is the wasm AOT time. Which of those takes 46 seconds? Both are surprising, the first should be fast unless you have a network lag or are preloading very many files (the devtools profiler can help figure that out). The second on that browser should compile in parallel using all your cores, so 46 seconds would mean either few cores or a very large codebase.
The second could be improved by using -Oz, or other code size reduction techniques. Although, if the 46 seconds is that and the codebase isn't massive, it might be worth filing a browser bug as you may have hit a current slow area. On Mon, Aug 29, 2016 at 9:27 PM, awt <[email protected]> wrote: > Sorry, I'm using O2 instead of Oz. > > > On Tuesday, August 30, 2016 at 12:17:49 PM UTC+8, awt wrote: >> >> Hi, >> >> I was trying out WebAssembly when I noticed that there is a significant >> lag sometimes between the 'trying binaryen method: native-wasm' and >> 'binaryen method succeeded' message or getting to the 'trying binaryen >> method: native-wasm' message itself . It normally takes up to 46sec on my >> machine. >> >> The following are my setup info: >> >> 1. Browser: Nightly 51.0a1 (2016-08-09) >> 2. Emscripten: 1.36.7 >> 3. Build Flags: -s BINARYEN=1 -Oz >> 4. Size of wasm: 3.75mb >> >> Is there any way in which we can speed up the boot up time? >> > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
