In my view, there is enough information to deduce, with a high level of certainty, that single-threaded compilation performance (in general) is far too slow in chrome, and that this is a problem, irrespective of how fast or slow it happens to be in any other browser.
If there's additional insight to be gained from comparing single-threaded wasm compilation performance between any two browsers, I think that comparison can be made by any interested party, independently. On Thursday, December 13, 2018 at 1:55:36 PM UTC-5, Dan Gohman wrote: > > > > > > On Tue, Dec 11, 2018 at 5:03 PM Goran Milovanovic <goranm...@gmail.com > <javascript:>> wrote: > >> >> Performance seems to depend heavily on the number of available hardware >> threads, and is far too poor on machines that only have a few. >> >> In short: Single-threaded performance seems abysmal, so that would be the >> thing to look into. >> >> I don't know if it's faster or slower in firefox. I suspect it's >> comparable, but I don't find it interesting/relevant enough to test. >> > > It might give us more insight into whether you're "hitting a base case in > the VM", or whether "this is a problem in the browsers, or in the > emscripten toolchain, or somewhere else", which seem to have been topics of > interest in this thread :-). > > Dan > > -- 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.
