Running lightweight models on the edge gateway: latency vs privacy阅读 2.8k
Move inference from the cloud to the gateway so sensor data can stay on-site for anomaly detection and simple decisions.
AI × IoT
Articles load from mercor_blog.sqlite3 when present; else from MySQL when MYSQL_* is set; otherwise static demo posts. Sidebar filters by keyword or topic tag.
Move inference from the cloud to the gateway so sensor data can stay on-site for anomaly detection and simple decisions.
Ship updates without bricking devices—partitioning, dual-bank images, and canary groups.
Bridge plant floors to telemetry buses without melting your broker or historians.
Plan capacity before you deploy hundreds of nodes in one yard.
From a single project to multi-tenant setups—how to name topics and model shadow state without painting yourself into a corner.
Keep scans predictable and map registers to a clean thing model upstream.
Start with assets, alarms, and throughput—not every bolt on day one.
Seasonality and maintenance windows will fool naive thresholds—plan for them.
Vectorize metric summaries and alert text so you can query historical conditions and runbooks in conversation.
Match orchestration weight to power, staff skills, and offline tolerance.
Keep query latency sane while preserving evidence for audits.
Design alert delivery so duplicate bursts do not page the whole team.
Pick the contract style that matches your connectivity and client stacks.
Reduce false positives when doors open or trucks reload.
Ship useful vision features without storing more pixels than you need.
Treat the PLC as the source of truth for physical state.
Separate namespaces early so one customer cannot enumerate another’s fleet.
Use version vectors or last-writer-wins with explicit domains.
Normalize units and clock skew before comparing sites.
Without failure history, start with health scores—not magic failure dates.
Showing 1–20 of 50 articles