On Fri, Jun 5, 2020 at 7:40 AM MEENA N SUBBIAH wrote:
> I finally found out why my build is slower.
>
> I build the wasm on a windows subsystem for linux, it was slower.
> The when I build the same on a mac machine it is faster.
>
> Is this expected behaviour?
>
>
No, you should get identical
The OS you use when building the wasm shouldn't affect its contents or how
fast it is. If you set EMCC_DEBUG=1 for the fast build and the slow build
you might be able to see where the difference is.
On Fri, Jun 5, 2020 at 7:40 AM MEENA N SUBBIAH wrote:
> I finally found out why my build is
I finally found out why my build is slower.
I build the wasm on a windows subsystem for linux, it was slower.
The when I build the same on a mac machine it is faster.
Is this expected behaviour?
steps to build -
1. clone the code from https://github.com/ankh-g/libvpx/tree/wartc (branch
For LTO you also need to pass -flto during the compile step (and during
link, and you don't need `--llvm-lto 3` any more, which was for the old
backend).
If that's not it, I'd suggest comparing profiles between the builds to find
what is actually slower in your build.
On Sat, May 30, 2020 at
I am trying to compile the libvpx module to wasm.
But I am facing huge performance issues.
The wasm I build takes an average encode time of 1300+ milliseconds.
But I found another livpx.wasm
https://github.com/webrtc/apprtc/tree/wartc/src/web_app/wasm/libvpx which
takes average encode time of
