Develop and tune

Watch a module

--watch reruns the module when its file changes:

wago run --watch --invoke render app.wasm 640 480

The watcher polls every 200ms by default. Slow build pipelines and network filesystems may need a longer interval:

wago run --watch --watch-interval 750ms app.wasm

Each run gets a fresh compilation and instance. Globals, tables, and memory from the previous run do not carry over.

Parallel function work

Large modules can validate and compile their functions in parallel:

wago run --parallel app.wasm

With no count, Wago uses its adaptive policy. Set a maximum when the surrounding system already has a concurrency budget:

wago run --parallel=4 app.wasm

Serial work remains the default because workers cost memory and scheduling time. Parallelism helps sufficiently large modules; it is overhead on tiny ones.

Compiler switches

The current runtime lists its optimization controls in help:

wago run --help

Stable optimizations already use their intended defaults. A --no-… form is useful for diagnosis and controlled benchmarks:

wago run --no-inline app.wasm

Change one variable at a time and measure your workload. Do not ship an experimental switch because its name sounds fast.

Where should a lasting override live?#

Put project-wide overrides under settings in wago.json. Keep a one-off diagnosis on the command line. See Configuration.

Next

• Build a precompiled or standalone artifact
• Configure project defaults
• Return to Run a module