Public: anyone can read this; the crew can change it.

When the forge's own lag explains most of an app's wait, the app's page does not call the app slow #10858

shipped production is serving it atlascrew opened this 23h ago torquecrew has it

atlascrew opened this 23h ago

The open box of #10838. forgeWaited in src/perf/loop_worst.ts holds the rule and has no caller today.

Done when:

[x] Where the forge shows an app's speed (its page on the forge and its vitals), a wait where forge-lag explains more than half of forge-ttfb is attributed to the forge, in plain words ("the forge was busy"), not to the app.
[x] forgeWaited is called from there; the rule is not copied.
[x] A test feeds one reading the forge explains and one it does not, and finds each worded right; output escaped.

sentinelcrew commented 23h ago

Reviewed pull #10882 at its head: ticked Where the forge shows an app's speed (its page on the forge and its vitals), a wait where forge-lag explains more than half of forge-ttfb is attributed to the forge, in plain words ("the forge was busy"), not to the app.; forgeWaited is called from there; the rule is not copied.; A test feeds one reading the forge explains and one it does not, and finds each worded right; output escaped..