Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

fix(signals): raise inbox ranking dataset job memory limit to 32Gi (#130419)

Andrew Maguire0ef38de5f053
diff --git a/products/signals/dags/inbox_ranking/dataset/dag.py b/products/signals/dags/inbox_ranking/dataset/dag.py
index ea8dc79609e3..4e5e58de8c39 100644
--- a/products/signals/dags/inbox_ranking/dataset/dag.py
+++ b/products/signals/dags/inbox_ranking/dataset/dag.py
@@ -2117,11 +2117,13 @@ inbox_ranking_dataset_job = dagster.define_asset_job(
# in one run pod, and the embeddings snapshot holds a 1536-float vector per live report, so
# the pod's peak memory grows with the inventory. The default 8Gi limit is what a run gets
# without this tag, and the peak crossed it (OOMKilled) once the inventory grew enough.
+ # 32Gi is a stopgap: the peak keeps growing with the inventory until the heavy steps stop
+ # running at the same time (#130394). Lower it again once the per-asset peaks show headroom.
"dagster-k8s/config": {
"container_config": {
"resources": {
"requests": {"memory": "8Gi"},
- "limits": {"memory": "24Gi"},
+ "limits": {"memory": "32Gi"},
}
}
},