No description
Graham McIntire
c7e7472c57
Weather.find_nearest_hrrr/3 and Weather.find_nearest_native_profile/3 run a three-range scan gated first by a ±1h valid_time window, then by a ±0.07° lat/lon box. The existing unique `(lat, lon, valid_time)` index is only usable on its `lat` prefix for these queries, forcing Postgres to scan wide lat slices before applying the valid_time filter — expensive on the Turing Pi 2 node. Add a `(valid_time, lat, lon)` composite so valid_time leads, collapsing the search to a narrow btree slice inside a single partition before the lat/lon box filter kicks in. `hrrr_profiles` is RANGE-partitioned by valid_time, so CREATE INDEX CONCURRENTLY is applied per partition and the resulting indexes are attached to a parent index created ON ONLY the partitioned table. `hrrr_native_profiles` is a regular table, so the concurrent build runs directly on it. |
||
|---|---|---|
| .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