Optimized code does enable asm.js. It is surprising that firefox is 5x slower than native, 2x is the expected amount.
There are some notes on optimizing, profiling, etc. here: https://github.com/kripken/emscripten/wiki/Optimizing-Code If you can make a public website of a profiling build, I can take a look at it too. - Alon On Mon, Apr 14, 2014 at 3:43 PM, Mark Hahn <[email protected]> wrote: > I turned off debug and enabled optimization and a big chunk of converted C > now runs in 2 seconds when it ran in 40 secs before. I'm using -O2 in the > compiler and -O1 in the linker. It runs natively in 1 second on a fast > x86. I'm very pleased with the 2X performance. > > This is in chrome. In firefox it takes about 5 secs. Chrome is version 36 > and FF is 28. > > Any idea how firefox could be so much slower? Doesn't the optimization > turn on asm.js? > > -- > 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.
