alexcrichton opened PR #13555 from alexcrichton:limit-handle to bytecodealliance:main:
This interface can in theory have backpressure built-in to it but this seems like something that's best left to the embedder to configure externally because it's basically easier to do it externally than internally. This then additionally adds some example rate limiting to
wasmtime serveto showcase what limiting might look like -- for example now there are CLI flags for configuring the maximum limit of concurrent TCP connections in addition to the maximum number of concurrent requests that can be in flight at once.<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested pchickey for a review on PR #13555.
alexcrichton requested wasmtime-wasi-reviewers for a review on PR #13555.
alexcrichton requested wasmtime-core-reviewers for a review on PR #13555.
:thumbs_up: pchickey submitted PR review.
alexcrichton added PR #13555 Document that ProxyHandler::handle does not handle backpressure to the merge queue.
github-merge-queue[bot] removed PR #13555 Document that ProxyHandler::handle does not handle backpressure from the merge queue.
alexcrichton added PR #13555 Document that ProxyHandler::handle does not handle backpressure to the merge queue.
:check: alexcrichton merged PR #13555.
alexcrichton removed PR #13555 Document that ProxyHandler::handle does not handle backpressure from the merge queue.
Last updated: Jul 29 2026 at 05:03 UTC