Generally you should first compile and run your code without optimizations (the default). Once you are sure that the code runs correctly, you can use the techniques in this article to make it load and run faster.
For example, to compile with optimization level
emcc -O2 file.cpp
The higher optimization levels introduce progressively more aggressive optimization, resulting in improved performance and code size at the cost of increased compilation time. The levels can also highlight different issues related to undefined behavior in code.
The optimization level you should use depends mostly on the current stage of development:
When first porting code, run emcc on your code using the default settings (without optimization). Check that your code works and debug and fix any issues before continuing.
Build with lower optimization levels during development for a shorter compile/test iteration cycle (
-O2 to get a well-optimized build.
-Os can produce an ever better build than
-O2, and are worth considering for release builds.
-O3 builds are even more optimized than
-O2, but at the cost of significantly longer compilation time and potentially larger code size.
-Os is similar in increasing compile times, but focuses on reducing code size while doing additional optimization. It’s worth trying these different optimization options to see what works best for your application.
Other optimizations are discussed in the following sections.
The meanings of the emcc optimization flags (
-O1, -O2 etc.) are similar to gcc, clang, and other compilers, but also different because optimizing WebAssembly includes some additional types of optimizations. The mapping of the emcc levels to the LLVM bitcode optimization levels is documented in the reference.
Compiling source files to object files works as you’d expect in a native build system that uses clang and LLVM. When linking object files to the final executable, Emscripten does additional optimizations as well depending on the optimization level:
For wasm, the Binaryen optimizer is run. Binaryen does both general-purpose optimizations to the wasm that LLVM does not, and also does some whole-program optimization. (Note that Binaryen’s whole-program optimizations may do things like inlining, which can be surprising in some cases as LLVM IR attributes like
noinline have been lost at this point.)
Emscripten also optimizes the combined wasm+JS, by minifying imports and exports between them, and by running meta-dce which removes unused code in cycles that span the two worlds.
Emscripten will emit WebAssembly by default. You can switch that off with
This section describes optimisations and issues that are relevant to code size. They are useful both for small projects or libraries where you want the smallest footprint you can achieve, and in large projects where the sheer size may cause issues (like slow startup speed) that you want to avoid.
You may wish to build the less performance-sensitive source files in your project using -Os or -Oz and the remainder using -O2 (-Os and -Oz are similar to -O2, but reduce code size at the expense of performance. -Oz reduces code size more than -Os.)
Separately, you can do the final link/build command with
-Oz to make the compiler focus more on code size when generating WebAssembly module.
In addition to the above, the following tips can help to reduce code size:
Use the closure compiler on the non-compiled code:
--pre-js, for example) then you need to make sure it uses closure annotations properly.
Floh’s blogpost on this topic is very helpful.
Make sure to use gzip compression on your webserver, which all browsers now support.
The following compiler settings can help (see
src/settings.js for more details):
Disable inlining when possible, using
-sINLINING_LIMIT. Compiling with -Os or -Oz generally avoids inlining too. (Inlining can make code faster, though, so use this carefully.)
You can use the
-sFILESYSTEM=0 option to disable bundling of filesystem support code (the compiler should optimize it out if not used, but may not always succeed). This can be useful if you are building a pure computational library, for example.
ENVIRONMENT flag lets you specify that the output will only run on the web, or only run in node.js, etc. This prevents the compiler from emitting code to support all possible runtime environments, saving ~2KB.
Link Time Optimization (LTO) lets the compiler do more optimizations, as it can
inline across separate compilation units, and even with system libraries.
LTO is enabled by compiling objects files with
-flto. The effect of this
flag is to emit LTO object files (technically this means emitting bitcode). The
linker can handle a mix wasm object files and LTO object files. Passing
-flto at link time will also trigger LTO system libraries to be used.
Thus, to allow maximal LTO opportunities with the LLVM wasm backend, build all
source files with
-flto and also link with
-sEVAL_CTORS will evaluate as much code as possible at
compile time. That includes both the “global ctor” functions (functions LLVM
emits that run before
main()) as well as
main() itself. As much as can
be evaluated will be, and the resulting state is then “snapshotted” into the
wasm. Then when the program is run it will begin from that state, and not need
to execute that code, which can save time.
This optimization can either reduce or increase code size. If a small amount of code generates many changes in memory, for example, then overall size may increase. It is best to build with this flag and then measure code and startup speed and see if the tradeoff is worthwhile in your program.
You can make an effort to write EVAL_CTORS-friendly code, by deferring things
that cannot be evalled as much as possible. For example, calls to imports stop
this optimization, and so if you have a game engine that creates a GL context
and then does some pure computation to set up unrelated data structures in
memory, then you could reverse that order. Then the pure computation could run
first, and be evalled away, and the GL context creation call to an import would
not prevent that. Other things you can do are to avoid using
getenv(), and so forth.
Logging is shown when using this option so that you can see whether things can
be improved. Here is an example of output from
trying to eval __wasm_call_ctors ...partial evalling successful, but stopping since could not eval: call import: wasi_snapshot_preview1.environ_sizes_get recommendation: consider --ignore-external-input ...stopping
The first line indicates an attempt to eval LLVM’s function that runs global
ctors. It evalled some of the function but then it stopped on the WASI import
environ_sizes_get, which means it is trying to read from the environment.
As the output says, you can tell
EVAL_CTORS to ignore external input, which
will ignore such things. You can enable that with mode
2, that is, build
trying to eval __wasm_call_ctors ...success on __wasm_call_ctors. trying to eval main ...stopping (in block) since could not eval: call import: wasi_snapshot_preview1.fd_write ...stopping
Now it has succeeded to eval
__wasm_call_ctors completely. It then moved on
main, where it stopped because of a call to WASI’s
fd_write, that is,
a call to print something.
The previous section on reducing code size can be helpful on very large codebases. In addition, here are some other topics that might be useful.
If you hit memory limits in browsers, it can help to run your project by itself, as opposed to inside a web page containing other content. If you open a new web page (as a new tab, or a new window) that contains just your project, then you have the best chance at avoiding memory fragmentation issues.
If your module is large enough that the time to download and instantiate it is noticeably affecting your application’s startup performance, it may be worth splitting the module and deferring the loading of code that is not necessary to bring up the application. See Module Splitting for a guide on how to do this. Note that module splitting is an experimental feature and subject to change.
Catching C++ exceptions (specifically, emitting catch blocks) is turned off by default in
-O1 (and above). Due to how WebAssembly currently implement exceptions, this makes the code much smaller and faster (eventually, wasm should gain native support for exceptions, and not have this issue).
To re-enable exceptions in optimized code, run emcc with
-sDISABLE_EXCEPTION_CATCHING=0 (see src/settings.js).
When exception catching is disabled, a thrown exception terminates the application. In other words, an exception is still thrown, but it isn’t caught.
Even with catch blocks not being emitted, there is some code size overhead unless you build your source files with
-fno-exceptions, which will omit all exceptions support code (for example, it will avoid creating proper C++ exception objects in errors in std::vector, and just abort the application if they occur)
C++ run-time type info support (dynamic casts, etc.) adds overhead that is sometimes not needed. For example, in Box2D neither rtti nor exceptions are needed, and if you build the source files with
-fno-rtti -fno-exceptions then it shrinks the output by 15% (!).
-sALLOW_MEMORY_GROWTH allows the total amount of memory used to change depending on the demands of the application. This is useful for apps that don’t know ahead of time how much they will need.
Enable Debug mode (EMCC_DEBUG) to output files for each compilation phase, including the main optimization operations.
A few UNSAFE optimizations you might want to try are:
--closure 1: This can help with reducing the size of the non-generated (support/glue) JS code, and with startup. However it can break if you do not do proper Closure Compiler annotations and exports. But it’s worth it!
To ensure that compiled code contains enough information for profiling, build your project with profiling as well as optimization and other flags:
emcc -O2 --profiling file.cpp
Emscripten-compiled code can currently achieve approximately half the speed of a native build. If the performance is significantly poorer than expected, you can also run through the additional troubleshooting steps below:
Test on multiple browsers. If performance is acceptable on one browser and significantly poorer on another, then file a bug report, noting the problem browser and other relevant information.