No description
Graham McIntire
6d914614ac
Previous pipeline held three overlapping large structures in RAM: 1. `merged: HashMap<Key, HashMap<String, f32>>` — 92k outer × ~60 String keys inner = ~200 MB of fragmented heap 2. `per_band: HashMap<u32, Vec<ScorePoint>>` — all 23 bands × 92k ScorePoints before the first write 3. A `scores.clone()` per band during the write loop (doubled that band's footprint transiently) Consolidate into: - Consume `merged` into a compact `Vec<(lat, lon, Conditions, BandInvariants)>`; the huge String-keyed HashMaps drop as soon as collection finishes. - Loop over bands: score → write → vector drops at end of iteration. One band's ~1.8 MB score vector lives at a time. Peak heap goes from ~1.5 Gi to ~250 Mi on the chain step. 2 Gi limit stays, but we now have 8× headroom instead of tight-fit. |
||
|---|---|---|
| .forgejo/workflows | ||
| .github | ||
| assets | ||
| bin | ||
| config | ||
| docs | ||
| k8s | ||
| lib | ||
| lib_ml | ||
| notebooks | ||
| priv | ||
| rel | ||
| rust/prop_grid_rs | ||
| scripts | ||
| test | ||
| vendor | ||
| .credo.exs | ||
| .dockerignore | ||
| .formatter.exs | ||
| .gitignore | ||
| .tool-versions | ||
| AGENTS.md | ||
| algo.md | ||
| app.json | ||
| CLAUDE.md | ||
| Dockerfile | ||
| elevation.md | ||
| mix.exs | ||
| mix.lock | ||
| prediction.md | ||
| README.md | ||
| tail_logs.sh | ||
| updates.md | ||
Microwaveprop
To start your Phoenix server:
- Run
mix setupto install and setup dependencies - Start Phoenix endpoint with
mix phx.serveror inside IEx withiex -S mix phx.server
Now you can visit localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.
Learn more
- Official website: https://www.phoenixframework.org/
- Guides: https://hexdocs.pm/phoenix/overview.html
- Docs: https://hexdocs.pm/phoenix
- Forum: https://elixirforum.com/c/phoenix-forum
- Source: https://github.com/phoenixframework/phoenix