Hey, I didn't - but from the top of my head I would think the perfomance is similar. Because the biggest bottleneck is still the fact that the WASM module is containerized (it inherits it's downsides) otherwise high-level runtime wouldn't be able to manage it. In other words both CRIO and containerd works with container primitives and not WASM modules directly if that makes sense.