File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -45,8 +45,21 @@ primary_region = "sjc"
4545 WARM_ENABLED = " true"
4646 WARM_INTERVAL_SECONDS = " 60"
4747 WARM_ACTIVE_WINDOW_SECONDS = " 1209600"
48- WARM_BATCH_CAP = " 200"
49- WARM_CONCURRENCY = " 8"
48+ # Sized to keep the whole active set fresh: ~1330 active feeds at a 180s refresh
49+ # threshold need ~440 refreshes/tick (1330 × 60/180) to never go stale. Cap 500
50+ # covers that with margin. Cheap now that WARM_MENTIONS is off (load dropped from
51+ # ~0.8 to ~0.04 once the mention fan-out was removed). Concurrency raised so a few
52+ # 30s-timeout feeds can't stall the drain within a 60s tick.
53+ WARM_BATCH_CAP = " 500"
54+ WARM_CONCURRENCY = " 16"
55+ # Pre-warming network-wide mention counts (Constellation fan-out) is OFF. It was a
56+ # pathological amplification — 25 items × ~1330 feeds × ~14 Constellation calls per
57+ # tick, with 30s timeouts piling up — and measured as ~all of the machine's load
58+ # (2026-06-26 A/B). Mentions still enrich lazily on read (POST /mentions triggers a
59+ # background enrich), so the only loss is pre-warm: counts fill in a poll later on
60+ # brand-new articles. Turning this back on requires real global rate-limiting first,
61+ # not just a bigger cap.
62+ WARM_MENTIONS = " false"
5063 # /extract concurrency cap. /extract fetches up to 10 MB of HTML and builds a
5164 # full DOM (Defuddle) — several × the raw bytes in memory — so unbounded
5265 # concurrency is the realistic OOM path on this 1 GB machine. Excess callers
You can’t perform that action at this time.
0 commit comments