You can increase certain system scaling limits using system scaling parameters. You can specify system scaling parameters using configuration keys when you create a software broker instance (see Setting Scaling Parameters Using Configuration Keys). You can also change system scaling parameters while the software broker is running using the Solace CLI (see Setting Scaling Parameters for a Single Software Event Broker and Setting Scaling Parameters for an HA Group).
For details about the minimum system resources required, see System Resource Requirements.
To see the current values of the system scaling parameters, run the show system command in the Solace CLI, and look at the Scaling section of the output:
solace-vmr> show system
System Uptime: 0d 0h 24m 9s
Last Restart Reason: User shutdown
Scaling:
Max Connections: 1000
Max Queue Messages: 3000M
Topic Routing:
Subscription Exceptions: Enabled
Subscription Exceptions Defer: Enabled
You can configure the following system scaling parameters:
If you increase the value of these system scaling parameters, the event broker will require additional resources. For more information, see Additional System Resources, below.
Maximum Number of Client Connections
You can increase the number of concurrent client connections supported by the event broker using the max-connections system scaling parameter. By default, the broker is limited to 100 concurrent client connections, but it can be provisioned for up to 200,000 connections assuming that sufficient system resources are provided.
| PubSub+ Broker | Default Concurrent Client Connections | Maximum Possible Concurrent Client Connections |
|---|---|---|
| PubSub+ Standard | 100 | 1,000 |
| PubSub+ Enterprise | 100 | 200,000 |
The following functionality is not available on software event brokers configured for a maximum of 100 client connections:
To use these features, configure your software event brokers with a higher maximum number of client connections.
For PubSub+ Standard Edition, if you set the max-connections system scaling parameter higher than the maximum supported, the broker will fail to start.
The number of current client connections cannot be changed on a broker configured as a monitoring node in an HA group.
A number of related system limits (for example, the maximum number of client usernames and subscriptions) are automatically scaled to values appropriate for the permitted number of client connections; see the System Limits and Alerts spreadsheet (available from the Solace Products site) for more information regarding those system limits.
Setting the Number of Concurrent Open Files for Container Images
To ensure reliable operation of the event broker, you must also increase the maximum number of concurrent open files per process when the maximum number of client connections is increased. The maximum number of concurrent open files for the container processes is governed by the nofiles resource limit. Most container runtimes support setting rlimit values using the ulimit parameter when creating a container. For example, in Docker Engine and Podman, for 10,000 client connections, add the --ulimit nofile=2448:42192 command line parameter when you create the container.
| Resource Limit | Maximum Client Connections | ||||
|---|---|---|---|---|---|
| 100 | 1,000 | 10,000 | 100,000 | 200,000 | |
| nofiles | 2448:6592 | 2448:10192 | 2448:42192 | 2448:222192 | 2448:422192 |
Maximum Number of Queue Messages
You can increase the number of queue messages (references to messages queued for delivery to consumers) supported by the event broker using the max-queue-messages system scaling parameter. By default, the broker is limited to 100 million queue messages and can be provisioned up to 3 billion, provided sufficient system resources are provided.
| PubSub+ Broker | Default Maximum Queue Messages | Maximum Possible Queue Messages |
|---|---|---|
| PubSub+ Standard | 100,000,000 | 240,000,000 |
| PubSub+ Enterprise | 100,000,000 | 3,000,000,000 |
For PubSub+ Standard Edition, if you set the max-queue-messages system scaling parameter higher than the maximum supported, the broker will fail to start.
The maximum number of queue messages cannot be changed on a broker configured as a monitoring node in an HA group.
Additional System Resources
The resource requirements for the minimum (default) values of the system scaling parameters are listed in System Resource Requirements.
If you increase the value of any system scaling parameters, the event broker will require additional resources. To see how the system resource requirements change with higher values of system scaling parameters, use the System Resource Calculator.