Skip to main content

Compute

The Collector is light. In a two-hour load test, one Collector served 5,000 devices polled every 60 seconds, including encrypted video-codec sessions, and used: Use grows roughly in line with the number of devices. We recommend: The recommended host leaves ample headroom for slower cloud vCPUs, heavier device types and WAN latency, and room for logs and the telemetry buffered during an outage (up to 256 MB; Outages, backup and replacement). In Google Cloud, for example, that’s an e2-custom-4-8192 or n4-highcpu-4 with a 50 GB balanced persistent disk.

When to add another Collector

Compute is rarely the limit. Add Collectors to match your network and how much you’re prepared to lose to one host failure:
  • A Collector would serve more than 5,000 devices.
  • A remote site is more than 50 ms away and has dozens of devices.
  • You want to isolate business units or environments from each other.
  • You want automatic failover: add a standby of the same size (see Outages, backup and replacement).
Packaging doesn’t affect sizing: a container with 4 vCPU and 8 GB behaves the same as a VM with 4 vCPU and 8 GB.

Bandwidth

Collector to M.A.R.C.U.S. Cloud (outbound HTTPS 443): about 0.11 Mbps per 1,000 devices at the default 60-second poll rate, covering telemetry, configuration sync and the command channel. A 5,000-device Collector sends about 0.6 Mbps. Allow twice that for estates with many devices that report in detail. Traffic from the cloud to the Collector is small, about 0.02 Mbps. Each open remote access session adds the device’s web page traffic, typically 1 to 5 MB when a page loads and little while it’s idle. After an outage, a Collector sends its buffered telemetry (up to 256 MB) as a one-off burst. Collector to devices depends on the device type: Video codecs dominate: without them, a typical estate averages about 0.2 kbps per device, so a 5,000-device Collector exchanges about 1 Mbps with its devices. Each Cisco codec adds about 14 kbps. For an on-premises Collector this traffic stays on the local network. For a cloud-hosted or central Collector it crosses each site’s WAN link, so size each link for its own devices: a site of 200 devices without codecs needs about 40 kbps. Halving the poll rate halves these figures. The display, AV-over-IP and Cisco figures were measured in the load test (the Cisco figure assumes a 100 KB status response); the others are calculated from how each adapter polls.

Cloud-hosted Collectors and egress

When Collectors run in a public cloud, the provider usually charges for traffic leaving it:
  • Collector to M.A.R.C.U.S. Cloud is egress: about 0.6 Mbps, or roughly 0.2 TB a month, per 5,000-device Collector.
  • Polling requests to devices over a VPN or interconnect are egress, but small: requests are a fraction of the device-side figures above.
  • Device replies arrive as ingress, which is usually free.
As a guide, an estate of 50,000 devices without codecs, on ten Collectors, comes to about 2–3 TB of chargeable egress a month.

Updated 23 Oct 2026 15:20 · page c8f7267