-
v0.8.0
Stablereleased this
2026-07-30 23:45:01 -05:00 | 240 commits to main since this releaseChanged
-
op.gg is now paced at one page per 12.5 s, taking the nightly crawl from
~14 minutes to ~2.5 hours. Derived rather than picked: the window makes 714
requests (5 tier lists + 271 counters + 271 runes for ranked, plus 5 + 81 + 81
for classic), and 9000 s / 714 ≈ 12.6 s.The old 1.5 s pacing walked the whole universe in a burst, and
champion-counterswas aborting at 55% coverage — the shape you get when
op.gg starts serving its 403 challenge page partway through. A 403 is
deliberately not retried, so once it starts, every remaining page fails
instantly and coverage collapses to however far the crawl got. This does not
prove that diagnosis, but bursting was the one thing under our control. -
COUNTERS_MAX_MINUTESandRUNES_MAX_MINUTESraised 45 → 70, and they are
coupled to the interval. At 12.5 s a 271-pair crawl needs ~57 minutes, so
the old 45-minute cap would have stopped it two thirds through and then
aborted it on coverage — turning a pacing change into a permanent outage.
Raise the caps with the interval or not at all. -
CLASSIC_ENABLEDnow defaults to OFF. Every other artifact is opt-out;
this one is opt-in. It adds ~167 requests to a window whose ranked half is
already failing for reasons nobody has established, and cumulative volume is
the last thing that should grow by default while that is open.
Notes
The crawl window probably needs widening, and this release does not do it.
CRAWL_START_HOUR=2/CRAWL_END_HOUR=5is three hours. An op.gg half taking
2.5 h of that leaves the Riot crawl ~30 minutes where it used to have ~2h45 —
andchampion-damageandchampion-benchmarksare both built from those rows,
so they would thin out night over night.02:00–07:00gives each half ~2.5 h.
That is a deployment decision, so it is flagged here rather than changed.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-