Ah ok I see, the old ASYNCIFY explains why the code is so big. I wonder if it is worth it or even possible to isolate the pieces that need asyncify, and only run those through the emterpreter, while the majority of code would be compiled to asm.js :)
-Floh. Am Mittwoch, 4. März 2015 13:13:46 UTC+1 schrieb 王璐: > > Sorry I didn't make it clear, the previous version was with the ASYNCIFY > version, which is likely to increase the size. Even 10x increase could be > common. > > There are ways of reducing size for ASYNCIFY, but it could be quite > complicated. > > > regards, > - Lu > > On Wednesday, March 4, 2015 at 7:19:25 PM UTC+8, Floh wrote: >> >> Aerhm, for some reason the embedded screenshot didn't make it and >> uploading doesn't work either at the moment :/ >> >> The timings from the Firefox network tools panel are (uncached) are: >> >> 92ms for vim.js at 704.52 KB and 392ms for vim.js.mem at 1,534.38 KB. The >> unrelated stuff actually took longer: 'forkme_on_github' PNG: 724ms, >> api.github.com callback: 265ms, etc... >> >> Great work! :) >> -Floh. >> >> Am Mittwoch, 4. März 2015 12:11:38 UTC+1 schrieb Floh: >>> >>> Wow, that's impressive! Startup is basically instant for me, here are >>> the timings (with disabled browser cache): >>> >>> >>> >>> The huge difference in compiled size is actually strange, Alon mentioned >>> in a tweet that the compressed size is similar. Did you compile the asm.js >>> version with one of the size-reduction options (like -Oz?)? In my >>> experience, uncompressed asm.js is about 5x bigger compared to native code, >>> and when gzipped, the difference nearly vanishes. >>> >>> Cheers, >>> -Floh. >>> >>> Am Mittwoch, 4. März 2015 05:32:57 UTC+1 schrieb 王璐: >>>> >>>> Hi all, >>>> >>>> Recently I tried EMTERPRETER on Vim.js, and I got this: >>>> http://coolwanglu.github.io/vim.js/emterpreter/vim.html >>>> >>>> I was compiling using -s EMTERPRETIFY=1 -s EMTERPRETIFY_ASYNC=1, >>>> without any WHITELIST or BLACKLIST, which means all the functions are >>>> interpreted? The file size is reduced significantly, comparing with the >>>> 26M >>>> monster-sized ASM.js version, this version with EMTERPRETER is only 2.5M, >>>> which improves the startup time a lot. >>>> >>>> While I was planning to optimize after making it work, I found the >>>> performance is good enough, I don't feel any delay for normal navigation >>>> or >>>> editing operations, but it does become slightly slower for commands like >>>> `%s/^/hello/g`, which inserts 'hello' at the beginning of each line. >>>> >>>> This interpreter is surprisingly faster than I had expected, probably >>>> there were already lots of async operations in Vim maybe? Anyway I'm quite >>>> happy with this new technique! >>>> >>>> Thanks! >>>> >>>> >>>> regards, >>>> - Lu >>>> >>>> >>> -- 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.
