a73x/mux

Watch

first-backoff tuning: reconnect pays 200ms-2s per tear #8

New issue

Open

opened 2026-08-13 06:35:02 +00:00 by a73x · 0 comments

a73x commented

2026-08-13 06:35:02 +00:00

(Migrated from git.a73x.sh)

Carried since M7. A reconnect after a tear can pay a 200ms-2s backoff step; measured ~4x win available on fast links, ~2x on slow (decisions.md M7). The schedule is now a documented inline expression in client.zig's reconnect (0 -> 200 -> x2 capped 2000); M15's survey suggested extracting it as a pure pinned nextBackoff() when touched.

Migrated from git-collab issue d909b10f34daa01a54f059bb68698371dd477b74.

Original author: a73x dev@a73x.sh.

Carried since M7. A reconnect after a tear can pay a 200ms-2s backoff step; measured ~4x win available on fast links, ~2x on slow (decisions.md M7). The schedule is now a documented inline expression in client.zig's reconnect (0 -> 200 -> x2 capped 2000); M15's survey suggested extracting it as a pure pinned nextBackoff() when touched. --- Migrated from git-collab issue `d909b10f34daa01a54f059bb68698371dd477b74`. Original author: a73x <dev@a73x.sh>.

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

a73x/mux#8

No description provided.