Checks: a watched game's standby search starves the first check of a followed live game #115

Closed
opened 2026-11-08 10:44:15 -05:00 by cmoriarty · 2 comments
Owner

A followed live game went 18 minutes without one check, because every read went to a watched game's standby search. It was ready about a minute after a check was asked for by hand.

What happens

Seen live on 2026-11-08 (1.2.0). The owner followed the Bengals and Liverpool at 15:20Z; both games were live.

Time (Z) Event
15:23:25 C Palace vs. Liverpool: stream found, tuned in the background; the owner then watched it
15:24:34 Liverpool: standby found
15:26:53 Liverpool: degrading, swapped to the standby (now none)
15:26:58 – 15:32:33 Liverpool: three standby reads, "no working stream", each leaving links for the next read
15:35:38 Liverpool: standby found
15:37:41 Liverpool: recovered via the standby (now none again)
15:38:03 – 15:38:16 Liverpool: two more standby reads
15:39:17 Falcons vs. Bengals: check asked for from the page
15:40:35 Falcons vs. Bengals: stream found on topsurge.st, link 2 of 5; in the background 5 s later

From 15:20 to 15:39 the Bengals game had no check at all. All the while, the Now table showed it as next, with an ETA of about 100 s.

Why:

  • prewarm.tick() fills one read slot per round (READ_CONCURRENCY, default 1). It goes in this order:
    1. renewals;
    2. a standby for each played game without one;
    3. requested reads;
    4. a second standby for each played game;
    5. followed standbys;
    6. readiness;
    7. followed second standbys.
  • While a watched game has no standby, or no second one, steps 2 and 4 take the slot every round.
  • The rounds are long: a round ends when its read ends, and these took up to 3.5 min across 24 links with several sites challenging the app's browser.
  • Each swap or recovery uses up the standby and starts the search again.
  • So a followed game with no stream at all waits for as long as the watched game is unsettled. A requested read (step 3) gets through only once the watched game has its first standby.

The idea

  1. A game with nothing beats a second option. A followed live game with no stream is read before a played game's second standby (step 4 moves after readiness).
  2. Take turns. When a played game's standby read finds nothing and a followed live game is waiting for its first check, the next round's slot goes to that game. The standby search resumes the round after, where its walk left off.
  3. The Now table tells the truth. "Next" names the read the coming round will actually take (a standby search for Liverpool, say), and the ETA counts the reads ahead of a waiting game.

Done when

  • In the unit lane, with one slot:
    • a played game whose standby reads find nothing, and a followed live game with no stream: the followed game is read within two rounds;
    • a played game with one standby and no second, and a followed live game with no stream: the followed game is read first;
    • a played game without a standby and no other game waiting keeps the slot every round, as now.
  • In the Admin view: now.next names the standby search when that is what the round takes, and a waiting game's ETA includes the reads ahead of it.
A followed live game went 18 minutes without one check, because every read went to a watched game's standby search. It was ready about a minute after a check was asked for by hand. ## What happens Seen live on 2026-11-08 (1.2.0). The owner followed the Bengals and Liverpool at 15:20Z; both games were live. | Time (Z) | Event | |---|---| | 15:23:25 | C Palace vs. Liverpool: stream found, tuned in the background; the owner then watched it | | 15:24:34 | Liverpool: standby found | | 15:26:53 | Liverpool: degrading, swapped to the standby (now none) | | 15:26:58 – 15:32:33 | Liverpool: three standby reads, "no working stream", each leaving links for the next read | | 15:35:38 | Liverpool: standby found | | 15:37:41 | Liverpool: recovered via the standby (now none again) | | 15:38:03 – 15:38:16 | Liverpool: two more standby reads | | 15:39:17 | Falcons vs. Bengals: check asked for from the page | | 15:40:35 | Falcons vs. Bengals: stream found on topsurge.st, link 2 of 5; in the background 5 s later | From 15:20 to 15:39 the Bengals game had no check at all. All the while, the Now table showed it as **next**, with an ETA of about 100 s. **Why:** - `prewarm.tick()` fills one read slot per round (`READ_CONCURRENCY`, default 1). It goes in this order: 1. renewals; 2. a standby for each played game without one; 3. requested reads; 4. a second standby for each played game; 5. followed standbys; 6. readiness; 7. followed second standbys. - While a watched game has no standby, or no second one, steps 2 and 4 take the slot every round. - The rounds are long: a round ends when its read ends, and these took up to 3.5 min across 24 links with several sites challenging the app's browser. - Each swap or recovery uses up the standby and starts the search again. - So a followed game with no stream at all waits for as long as the watched game is unsettled. A requested read (step 3) gets through only once the watched game has its first standby. ## The idea 1. **A game with nothing beats a second option.** A followed live game with no stream is read before a played game's second standby (step 4 moves after readiness). 2. **Take turns.** When a played game's standby read finds nothing and a followed live game is waiting for its first check, the next round's slot goes to that game. The standby search resumes the round after, where its walk left off. 3. **The Now table tells the truth.** "Next" names the read the coming round will actually take (a standby search for Liverpool, say), and the ETA counts the reads ahead of a waiting game. ## Done when - **In the unit lane, with one slot:** - a played game whose standby reads find nothing, and a followed live game with no stream: the followed game is read within two rounds; - a played game with one standby and no second, and a followed live game with no stream: the followed game is read first; - a played game without a standby and no other game waiting keeps the slot every round, as now. - **In the Admin view:** `now.next` names the standby search when that is what the round takes, and a waiting game's ETA includes the reads ahead of it.
Author
Owner

Closing: merged to develop in PR #119 (merge 73f86a3), milestone 39. It deploys once nobody is watching.

What changed:

  • A followed live game with no stream is now read before a played game's second standby.
  • A standby read that finds nothing owes the next round to a waiting check.
  • The Now table's next and ETA name the read the coming round really takes, and the queue chips are checks only, each game once.

Not seen live yet: a watched game's fruitless standby search giving way to a waiting game.

Closing: merged to develop in PR #119 (merge 73f86a3), milestone 39. It deploys once nobody is watching. **What changed:** - A followed live game with no stream is now read before a played game's second standby. - A standby read that finds nothing owes the next round to a waiting check. - The Now table's next and ETA name the read the coming round really takes, and the queue chips are checks only, each game once. **Not seen live yet:** a watched game's fruitless standby search giving way to a waiting game.
Author
Owner

Deployed 2026-11-08 17:27:26Z: commit 73f86a3, container a07efdae03b6, 36.6 s down, no errors in the log. Live: the Now table's next showed Falcons vs. Bengals' check with an ETA counting down.

Deployed 2026-11-08 17:27:26Z: commit 73f86a3, container a07efdae03b6, 36.6 s down, no errors in the log. **Live:** the Now table's next showed Falcons vs. Bengals' check with an ETA counting down.
Sign in to join this conversation.
No labels
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
cmoriarty/sports-breaker#115
No description provided.