Performance benchmark on a big network, posted on every PR
scripts/perf-bench.js times routing, a game day, an action, panels, the NOC dashboard and the map on tests/fixtures/big-network.json (104 POPs, 950 PNIs, 832 caches), base and head in alternating turns, and says whether routing results changed. perf.yml runs it on every PR against the base; perf-comment.yml posts the table as one updated comment. New performance skill, CLAUDE.md rule, PR template and docs.
This commit is contained in:
parent
ad8b1bebcb
commit
308c3f7045
13 changed files with 322 additions and 1 deletions
|
|
@ -39,6 +39,10 @@ A tour of the code is in [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
|
|||
must not depend on luck.
|
||||
- Add a bullet for players under `## [Unreleased]` in `CHANGELOG.md`, in plain English.
|
||||
Releases are cut by the maintainer.
|
||||
- Show the performance of changes to `site/` on a big network. The Performance check posts a table
|
||||
comparing your PR with `main` as a comment; to run it yourself:
|
||||
`git show origin/main:site/index.html > /tmp/base.html && npm run perf -- --base /tmp/base.html`.
|
||||
Anything marked slower needs an explanation.
|
||||
- Old saves must keep loading. New state needs a default for new games and a check in
|
||||
`sanitize()`.
|
||||
- Check your change on a phone-sized screen (about 360 px wide). Most players are on
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue