You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[wasm] Don't allocate jiterpreter AOT tables unless AOT was enabled at build time (#90978)
At present the jiterpreter has to allocate a lot of space for AOT-only optimizations. This PR flows through the RunAOTCompilation msbuild property when linking the wasm runtime JS, which allows us to skip allocating that space for applications that were not AOTed and improves startup performance.
// In degenerate cases the jiterpreter could end up generating lots of WASM, so shut off jitting once it reaches this limit
147
147
// Each wasm byte likely maps to multiple bytes of native code, so it's important for this limit not to be too high
148
148
DEFINE_INT(jiterpreter_wasm_bytes_limit, "jiterpreter-wasm-bytes-limit", 6*1024*1024, "Disable jiterpreter code generation once this many bytes of WASM have been generated")
149
-
DEFINE_INT(jiterpreter_table_size, "jiterpreter-table-size", 5*1024, "Size of the jiterpreter trace function table")
149
+
DEFINE_INT(jiterpreter_table_size, "jiterpreter-table-size", 6*1024, "Size of the jiterpreter trace function table")
150
150
// In real-world scenarios these tables can fill up at this size, but making them bigger causes startup time
151
151
// to bloat to an unacceptable degree. In practice this is still better than nothing.
152
152
// FIXME: In the future if we find a way to reduce the number of unique tables we can raise this constant
0 commit comments