The FPS numbers can only tell you that it's not too slow for your
computer. You should compare browser CPU usage with memory growth
enabled and disabled. Browser profilers will also show you what
percentage of CPU time you're using, but note that JavaScript runs a bit
slower when profiling.
DOSBox is very CPU intensive due to being an emulator and not using
hardware acceleration. All the game graphics are drawn by emulated x86
code and the frame buffer format is translated by software. The slowdown
may be acceptable in less CPU intensive software.
On 2015-02-24 05:07 PM, Bailey Hayes wrote:
I'm still seeing 50-60fps with Chrome Canary 64-bit (43.0.2314.0) on
OSX. I'm using options -Oz and ALLOW_MEMORY_GROWTH=1. The js artifact is
21MB (up from 18MB). I also tried Chromium on OpenSUSE. After reading
the discussion in 3907
<https://code.google.com/p/v8/issues/detail?id=3907>, I would expect to
see the same problems as Doom in Em-DOSBox. Is there something in that
scenario that I'm missing? We have a large project that extensively uses
OpenGL emulation (FULL_ES2=1) and multiple WebGL contexts.
--
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.
