Repository navigation
Consider optimizations to reduce the number of host calls #823
Description
While host calls are pretty fast these days, it's still useful to consider optimizations to reduce their number per request for really low-latency scenarios. This has come up in two areas so far:
- @PiotrSikora mentioned in this comment that many requests have empty bodies, so perhaps
consumecould short-circuit the hop throughincoming-stream, maybe with a variant like this. - @brendandburns mentioned in this comment the sequence of calls to create headers, then create a response, then make the request. Perhaps we could have some more one-shot options that do multiple of these at once.
Both seem like potentially good ideas to me but I'd be happy to hear more thoughts.
Activity
brendandburns commentedon Mar 5, 2023
fwiw, part of the motivation to reduce host calls is also to improve the security of the surface area. I believe it is easier to ensure the security of a single
req(...)style call vs all of the memory manipulation of the various calls between guest and host.It's also a cleaner abstraction for the implementor, so fewer bugs in the implementation.
sw17ch commentedon Oct 8, 2026
The WASI HTTP champions looked at this in triage. Given the many changes that have occurred since this was opened, we're going to close this issue. We believe the best way forward is to let people open new issues with ways that specific performance bottlenecks can be improved.