I'm using chrome, and I just tested the asm.js build, which, to my 
surprise, actually starts up faster than the wasm build ... How can that 
be? I mean, maybe I misunderstood something about what wasm is supposed to 
deliver, but wasn't faster compile time one of the touted benefits?


On Saturday, April 7, 2018 at 3:11:44 PM UTC-4, caiiiycuk wrote:
>
> What browser do you use? For me Chrome is dramatically slow while 
> compiling wasm, asm.js is faster at least 3 times. 
>
> 2018-04-08 1:19 GMT+07:00 Goran Milovanovic <goranm...@gmail.com 
> <javascript:>>: 
> > After all the files are downloaded, it takes ~5 seconds for my program 
> to 
> > actually start. Since my cpu cores are basically pegged at 100% during 
> that 
> > time, I assume that the emscripten runtime is doing some kind of code 
> > processing, but I'm confused as to why it takes so long, because I'm 
> using 
> > WASM, and one of the core benefits of that was supposed to be really 
> fast 
> > stratup time. 
> > 
> > My wasm file is 3.5 MB, so it doesn't seem that large (at least not for 
> > something that was optimized for quick processing). 
> > 
> > Any relevant info would be appreciated. 
> > 
> > Thanks. 
> > 
> > -- 
> > 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 emscripten-discuss+unsubscr...@googlegroups.com <javascript:>. 
> > 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 emscripten-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to