Currently all jobs runs on a tokio::task which is okay for lightweight parallel tasks but when running
arbitrary WASM files we could encounter heavy-lifting tasks which involves intensive CPU usage.
To reduce the risk, and to better align with having multiple executors architecture we could benefit from
the spawn_blocking approach instead.
Currently all jobs runs on a
tokio::taskwhich is okay for lightweight parallel tasks but when runningarbitrary WASM files we could encounter heavy-lifting tasks which involves intensive CPU usage.
To reduce the risk, and to better align with having multiple executors architecture we could benefit from
the
spawn_blockingapproach instead.