Scaling Guide
NORTHSTARSHOW SYSTEMS
Scaling Guide
From a single node to a 500-node deployment
| Document Number | Revision | Date | Platform Version |
|---|---|---|---|
| NSSS-DOC-0014 | A | 2026-05-20 | 1.0 |
Capacity Limits
| Resource | Default Limit | Notes |
|---|---|---|
| Polaris nodes per HelmOS | ~500 | Single NUC; UDP heartbeats scale linearly |
| Concurrent cues | ~1000 | Each cue runs as an async task in HelmOS |
| Wi-Fi stations per AP | AP-dependent | See NSSS-DOC-0012; enterprise APs handle 100+ |
| Subnet hosts | 254 (/24) or 510 (/23) | Expand subnet at 200+ nodes |
| Cuemaster clients | ~50 concurrent | WebSocket fanout in HelmOS |
| Project size | 200 MB | HelmOS deploy endpoint cap |
Scaling Phases
1–10 nodes — Single Venue Pilot
One AP, one NUC, /24 subnet. Suitable for an escape room or small haunt. No special planning required.
10–100 nodes — Standard Production Venue
One or two APs on non-overlapping 5 GHz channels. Enterprise-class AP required. /24 subnet still ample. HelmOS performs comfortably on a low-end NUC.
100–250 nodes — Large Attraction
Multiple APs with handoff (802.11k/r/v). Survey for coverage at every node mount location before installing. Consider /23 subnet to leave DHCP headroom. NUC should have at least 8 GB RAM.
250–500 nodes — Theme Park Scale
Dedicated network design. Multiple APs, multiple subnets bridged. Plan for staggered boot to avoid boot-storm registration peaks at HelmOS. NUC should have a quad-core CPU and SSD.
Boot Storm Mitigation
When power is restored after an outage, every Polaris node boots simultaneously. Within 30 seconds, all of them attempt to associate with the AP and POST to /api/nodes/register. The Polaris firmware includes random backoff on registration failure, but for large venues consider staggering power circuits so groups of nodes boot in waves.
When to Run Multiple Helms
A single HelmOS instance can manage 500+ nodes. The reason to deploy multiple Helms is operational, not technical:
- Independent zones in a campus — each Helm owns its area
- Pre-production / staging — a dev Helm separate from the show Helm
- Fail-over readiness — a warm spare Helm with the same .nsss.compose loaded
Related Documents
- NSSS-DOC-0010Architecture Overview
- NSSS-DOC-0012TrueNorth Network Design
Revision History
| Revision | Date | Description |
|---|---|---|
| A | 2026-05-20 | Initial publication |