Re: Chrome Wasm Performance Regression

[Charles Vaughn]

During a perf investigation on the product I work on, we saw 64 take 400ms 
for compiling, while 66 showed 200ms. We didn't have numbers for 63 and 
just assumed it was general perf progress.

On Wednesday, March 7, 2018 at 6:48:56 AM UTC-8, jj wrote:
>
> Yikes, this sounds really bad, haven't heard about this issue before. 
> Try writing up the data points you have to Chromium's bug tracker, 
> here's one earlier bug report to Chromium about WebAssembly, which has 
> a good list of relevant people at Google to CC as well: 
> https://bugs.chromium.org/p/chromium/issues/detail?id=729768 
>
> Also checking out cold loading time on http://mzl.la/webassemblydemo 
> might be interesting. 
>
> 2018-02-09 15:07 GMT+02:00 Gaurav Dewan  >: 
> > In Chrome 64, the wasm initialization time has increased by 300-400% as 
> > compared to Chrome 63 (easily reproducible on windows machine - other 
> > platforms are impacted too) 
> > The issue is reproducible in "Tanks Demo" too - is it a known issue ? 
> > 
> > Thanks 
> > Gaurav 
> > 
> > -- 
> > 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. 
>

-- 
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.

Re: Chrome Wasm Performance Regression

[Jukka Jylänki]

Yikes, this sounds really bad, haven't heard about this issue before.
Try writing up the data points you have to Chromium's bug tracker,
here's one earlier bug report to Chromium about WebAssembly, which has
a good list of relevant people at Google to CC as well:
https://bugs.chromium.org/p/chromium/issues/detail?id=729768

Also checking out cold loading time on http://mzl.la/webassemblydemo
might be interesting.

2018-02-09 15:07 GMT+02:00 Gaurav Dewan :
> In Chrome 64, the wasm initialization time has increased by 300-400% as
> compared to Chrome 63 (easily reproducible on windows machine - other
> platforms are impacted too)
> The issue is reproducible in "Tanks Demo" too - is it a known issue ?
>
> Thanks
> Gaurav
>
> --
> 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.

-- 
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.