Broker requirements
The hardware needed by the Remote Control Broker depends on how the Broker is used: for On-Demand sessions only, or to serve a population of Unattended-mode targets.
Scope and assumptions
The figures provided on this page are valid only under the following
conditions:
- Sessions are established from the standalone Controller application. No validated figures are available when sessions are established from the Web Controller.
- The Broker runs on real physical hardware matching the specifications listed below. Performance can degrade on virtualized servers; an additional sizing margin is recommended in that case.
- Broker performance is driven mainly by the number of available CPU cores. Adding cores improves throughput more than adding RAM, provided the minimum RAM listed for the target population is met.
Reference environment
configuration
The figures on this page were measured with the Remote Control environment configured as follows. The same configuration is assumed when applying the Broker sizing in a real deployment; significant deviations from these values can change the supported workload.
| Property | Value | Location | Purpose |
|---|---|---|---|
| rc.unattended.heartbeat.interval.minutes | 2 mins | trc.properties (Server) | Heartbeat interval used by Unattended-mode targets. |
| heartbeat.timeout | 1440 mins | trc.properties (Server) | Time after which a target is marked offline if no heartbeat is received. |
| LogLevel | ERROR | trc.properties (Server) | Server log verbosity. Keep I/O overhead under control. |
| LogLevel | 1 | trc_broker.properties (Broker) | Broker log verbosity. Default is 2; lower to 1 to keep I/O overhead under control. |
When the broker is used for On-Demand sessions only:
- Processor: at least 1 GHz, on a supported operating system.
- Memory: 4 GB RAM (32-bit) or 8 GB RAM (64-bit) minimum.
- Disk: 120 MB minimum.
- Additional disk space for session video recordings. Recordings are stored temporarily; size depends on session length and on-screen activity. As a reference, a 5-minute session at 8-bit color uses about 2 MB; 24-bit true color recordings require more space.
When the broker is used for Unattended Targets up to 10000 - 16000 targets:
- Processor: two Quad core processors at 2.40 GHz, on a supported operating system.
- Memory: 4 GB RAM (32-bit) or 8 GB RAM (64-bit) minimum.
- Disk: 1 GB minimum.
- Additional disk space for session video recordings. Recordings are stored temporarily; size depends on session length and on-screen activity. As a reference, a 5-minute session at 8-bit color uses about 2 MB; 24-bit true color recordings require more space.
- Up to 10K Unattended targets set rc.unattended.heartbeat.interval.minutes = 2 (default).
- Up to 16K Unattended targets set rc.unattended.heartbeat.interval.minutes = 4.
Operating system support
The following operating systems are supported:
- Windows™ Server 2016
- Windows™ Server 2019
- Windows™ Server 2022
- Windows™ Server 2025
- Red Hat Enterprise Linux™ 7.0 or later
- Red Hat Enterprise Linux™ 8.0 or later
- Red Hat Enterprise Linux™ 9.0 or later
- SUSE Linux™ Enterprise Server 15 or later
Supported Architectures
- Intel™ 64 or AMD™64 (also known as x64, x86-64, EM64T)
Note: IA-64 (also known as Itanium™) processors are not supported.