eSlider
ea062af86a
Explorer and exporter were scanning the full Parquet lake every 1–5s (~2000 files, 200MB+), driving ~2.2 CPU cores. Limit metrics to the last N flights, cache DuckDB views and the partition tree, slow live polls to 2s, and keep drones alive after seal to stop restart churn. Add node-exporter, scan-duration metrics, and a Swarm Platform Grafana dashboard for node CPU/memory and scan health.
Swarm visualization prototype
A 2D top-down view of the swarm data plane from 04 — Swarm sync: drones patrol an area with static and mobile obstacles, exchange 5 Hz pose broadcasts (blue link flashes), and run opportunistic bulk sync of sealed partitions (green links with live rate and cumulative up/down counters).
No backend — a pure client-side simulation of the same behavioral model the Python simulator implements over real Parquet and UDP.
Run
npm install
npm run dev # http://localhost:5173
What to look at
- Links appear and disappear as drones move in and out of radio range; persistent links render semi-transparent, broadcast deliveries flash them briefly.
- Busy links turn green and show current rate plus total transferred (
↑/↓) — the bandwidth budget from the sync design made visible. - Per-drone label: id, current Wi-Fi channel (hopping), battery.
- Controls: drone count, simulation speed, pause.