R7: final stress run + tuning #38
Reference in New Issue
Block a user
Delete Branch "feature/r7-final-stress-tuning"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PRERELEASE.md R7 — Final stress run + tuning (staged; in progress).
This PR lands the pre-run changes; the agreed tuning +
REPORT-R7.md+ the doc/tracker bake-back are pushed to this same branch after the final stress run (R7 is a measure → tune → re-verify phase, so the tuning numbers follow the run).So far:
loadtest/): each virtual player owns its h2c connection instead of multiplexing over one sharedhttp2.Transport(the R2transport_errorartifact); finished games are dropped from the rotation.docker_statsreceiver; Resources dashboard retargeted.GOMAXPROCSon the contour (generous R2-derived starting values; tightened to prod sizing in Round 2).Still to come on this branch: the final run on the freshly-deployed contour, the agreed tuning values,
loadtest/REPORT-R7.md, and marking R7 done inPRERELEASE.md(+ docs).The receiver defaults to Docker API 1.25, but the contour daemon's minimum is 1.40 (it speaks up to 1.54), so otelcol crash-looped on start with "client version 1.25 is too old". Pinning api_version to 1.44 (accepted by both the receiver's bundled client and the daemon) starts the receiver cleanly — verified by running the image against the host socket ("Everything is ready", no start error).View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.