Stream: git-wasmtime

Topic: wasmtime / PR #13839 Set initial epoch deadline to `1` in...

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 14:28):

tschneidereit opened PR #13839 from tschneidereit:epoch-perf to bytecodealliance:main:

Setting the initial epoch deadline to 1 instead of the default 0 means that the deadline check doesn't immediately trigger. In local testing, this essentially eliminates the performance difference between wasmtime serve and wasmtime serve -W timeout=1 for a Rust Hello World WASIp2 component. In absolute terms, that means it goes from about 120k RPS to 155k RPS.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 14:28):

tschneidereit added the label wasmtime:serve on PR #13839.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 14:28):

tschneidereit requested fitzgen for a review on PR #13839.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 14:28):

tschneidereit requested wasmtime-core-reviewers for a review on PR #13839.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 14:54):

:thumbs_up: fitzgen submitted PR review:

Thanks!

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 14:54):

fitzgen added PR #13839 Set initial epoch deadline to 1 in HostHandlerState::instantiate to the merge queue

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 15:19):

:check: fitzgen merged PR #13839.

view this post on Zulip Wasmtime GitHub notifications bot (Jul 07 2026 at 15:19):

fitzgen removed PR #13839 Set initial epoch deadline to 1 in HostHandlerState::instantiate from the merge queue

Last updated: Jul 29 2026 at 05:03 UTC