Hi guys. I working on next version of js-dos, and I have some ideas where to go. I have couple questions to see which way is better.
Currently, js-dos is a WebAssembly binary (+asyncify changes) that does emulation in 16ms frames, and stops with emscripten_sleep for processing user input. So typical work flow is: 16ms emulation| <process user input> | 16ms emulation | <process user input> | etc. Typically <user input> is empty, and performance is limited by browser performance, and browser scheduler that stops emulation with emscripten_sleep. My first question is: 1. "Can I have any performance boost if I move emulation core inside worker?" >From my point of view it's not sens, because even in worker I should stop emulations every 16ms to process messages and send updates to page. Even If I do not account frames data (320x200 32bpp image), I think performance will be same as in regular integration. Am I wrong? My second questing: 2. "Is WASI perfromance is better than default WebView WebAsssembly core?" (android/ios) One of my target is provide js-dos also on mobiles (android/ios) and I think I can do it as is, or also I can do it with WASI. I think with WASI clients can integrate js-dos in more ways, but what about performance? Is it more preformant to use WASI instead of browser on mobiles, or they are same? -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAKOm%3DVFLTVLCiF6QnQWe7tg666Q8ni1jXb3yUbAYcT38ED7Sow%40mail.gmail.com.
