fix: revert prop-grid-rs memory limit to 3Gi after OOM at 1.5Gi
Some checks failed
Build and Push / Build and Push Docker Image (push) Failing after 5m50s
Some checks failed
Build and Push / Build and Push Docker Image (push) Failing after 5m50s
This commit is contained in:
parent
959f3a3f69
commit
b01757b9e3
1 changed files with 6 additions and 5 deletions
|
|
@ -139,11 +139,12 @@ spec:
|
||||||
# After the dense-grid rewrite (commit 63f25a96) the
|
# After the dense-grid rewrite (commit 63f25a96) the
|
||||||
# per-task grid footprint dropped from ~200-400 MB of
|
# per-task grid footprint dropped from ~200-400 MB of
|
||||||
# nested HashMaps to ~18 MB of dense f32 planes.
|
# nested HashMaps to ~18 MB of dense f32 planes.
|
||||||
# PARALLELISM went 1 → 3 in the same commit. The remaining
|
# PARALLELISM went 1 → 3 in the same commit. 1.5Gi was
|
||||||
# large term is the f00 native-level decode (~530 MB GRIB2
|
# attempted (commit db57b3a1) but the pod OOMed within
|
||||||
# + wgrib2 working set). 1.5Gi leaves headroom for three
|
# ~20s at that limit — the f00 native-level decode still
|
||||||
# concurrent chain steps plus one analysis step.
|
# carries a ~530 MB GRIB2 + wgrib2 working set. Hold at
|
||||||
memory: 1.5Gi
|
# 3Gi until RSS is profiled at steady state.
|
||||||
|
memory: 3Gi
|
||||||
securityContext:
|
securityContext:
|
||||||
allowPrivilegeEscalation: false
|
allowPrivilegeEscalation: false
|
||||||
runAsNonRoot: true
|
runAsNonRoot: true
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue