Improve communication with remote nodes
- Last UpdatedAug 12, 2025
- 1 minute read
The $WinPlatform object has a set of attributes associated with the Message Exchange (MX) protocol which allow fine tuning communication between galaxy components. When the network bandwidth is limited, the connection is intermittent, or the amount of objects is too large (thousand instances), it is recommended to adjust these parameters to obtain a better performance in deployment and communication.
It is important to keep in mind that the values may be changed based on specific conditions of operation. The values shown here are intended as a starting point for fine tuning the system. The following table shows the default values and recommended values for the MX parameters.
|
WinPlatform Object |
Default Value |
Recommended Value |
Comments |
|
Message time-out |
30000 ms |
300,000 ms |
Increase to avoid timeouts when deploying large number of instances |
|
NMX heartbeat period |
2000 ms |
2000 ms |
|
|
Consecutive missed NMX heartbeats allowed |
3 |
4 (Automation Object Server) 4 (Galaxy Repository) 4 (Visualization node) |
Increase to avoid false failovers in large systems |
For details on the attributes in the WinPlatform object, please refer to the $WinPlatform object Help.