dvb-WarpPool v1.12.2 — the energy dashboard stays fast even after months of solar data
A small, honest performance patch — relevant if you run your solar/PV system alongside the pool:
- The problem. With solar tracking enabled, the energy dashboard splits consumed energy into “solar” vs. “grid”. The query behind it joined a per-minute solar table to the miner telemetry on a computed key — which SQLite could only resolve as a nested-loop full scan. After a few months of PV history that took several seconds per call, and the dashboard runs it on a ~30s cadence → the log filled with “slow statement” warnings.
- The fix. The split now runs as a correlated per-bucket query, driven off the telemetry and backed by the solar table’s primary-key index. Result: hundreds of times faster (the hourly daily-rebuild ~2000×), and the computed kWh figures are byte-identical — only the speed changes, not a single number.
Honest framing: a pure performance fix for solar pools — no new feature, no hashrate or earnings effect, no behaviour or config change. If you don’t use solar tracking you were never affected and see nothing change (the solar table is empty). If you do run PV, your energy dashboard is snappy again and your log is quiet. 1021 tests green, reproducible build as always.
the Umbrel Bitcoin app reports: IPC mining interface is OFF” — even though IPC was live. Reason: Umbrel sets that variable at container start, so toggling later left the banner stale. It’s now gated on the actual socket test: the moment the test returns OK, the warning is gone. (On older builds, restarting the WarpPool app fixed it.)
