Documents why the test pin (5) and production default (50) are NOT
the same value despite both being 'fixes' for relay-side cliffs in
moq-relay 0.10.25. They are tuned for two distinct cliffs in the
same binary:
- Production cliff (need 50): per-stream rate. serve_group's task
pool can't tolerate any blocked open_uni().await — slower stream
creation gives the pool time to drain.
- Local interop cliff (need 5): per-stream byte volume. moq-relay
0.10.25's per-subscriber forward buffer holds the data side of
large groups on loopback.
Local environment (loopback, no loss, single subscriber) doesn't
reproduce the conditions (CWND collapse, transient stalls) that fire
the production cliff. So testing at framesPerGroup=5 is safe for
the interop env but actively wrong for production audio rooms.
Recommendation: status quo. Both kdocs already cross-reference the
field-test runs that justified each value. The only safe escalation
is to re-run HCgOY's two-phone field tests against the current
production deployment to confirm the cliff still hits at framesPerGroup=5.
No production code change.
Claude
d1210df858