https://github.com/bytecodealliance/javy/pull/793 introduced a performance regression for statically linked modules because the QuickJS context no longer loads the JS module during pre-initialization. This is unfortunately an expensive step though not enough to trigger our fuel consumption checks in tests.
Some thoughts on how to go about this are to retain the QuickJS runtime in compile_src by wizening when performing that step or augmenting initialize_runtime to also optionally load source code or bytecode.
https://github.com/bytecodealliance/javy/pull/793 introduced a performance regression for statically linked modules because the QuickJS context no longer loads the JS module during pre-initialization. This is unfortunately an expensive step though not enough to trigger our fuel consumption checks in tests.
Some thoughts on how to go about this are to retain the QuickJS runtime in
compile_srcby wizening when performing that step or augmentinginitialize_runtimeto also optionally load source code or bytecode.