rick/LEDMatrix
1
0
Fork 0
mirror of https://github.com/ChuckBuilds/LEDMatrix.git synced 2026-10-10 17:16:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(sports): state what ESPN_CHUNK_WORKERS was measured to do, not more

Browse Source 
The comment claimed the sequential fetch made scoreboards blow the 20s
startup update() timeout. A boot on this branch still deferred 12 plugins
and timed out baseball-scoreboard while its season fetches took 0.74s and
1.12s: the startup budget is spent on other per-plugin work. Say what was
measured -- 17.7s sequential, 2.6-3.3s concurrent -- and nothing else.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Chuck
2026-09-18 08:37:21 -04:00
co-authored by Claude Opus 5
parent f7e5a6a4d0
commit e26dff149e
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/common/espn_dates.py
+3 -4
View File
@@ -46,10 +46,9 @@ ESPN_MAX_LIMIT = 500
# How long a rejected range keeps later ranges from being tried as ranges. # How long a rejected range keeps later ranges from being tried as ranges.
RANGE_RETRY_SECONDS = 6 * 60 * 60 RANGE_RETRY_SECONDS = 6 * 60 * 60
# How many chunk requests may be in flight at once. A cold college-baseball # How many chunk requests may be in flight at once. Four busy months of
# season is ~130 chunks once the busy months are re-asked day by day; asking # college baseball are ~130 chunks once each is re-asked day by day: 17.7s one
# for them one at a time took long enough that scoreboard plugins blew the # at a time on a Pi 4, 2.6-3.3s six at a time. Kept under requests' default
# 20s update() timeout on first run. Kept under requests' default
# pool_maxsize of 10 so the shared Session never has to discard connections. # pool_maxsize of 10 so the shared Session never has to discard connections.
ESPN_CHUNK_WORKERS = 6 ESPN_CHUNK_WORKERS = 6