Large Grid configuration tips for better Manager performance (GridSever 4.1)
Article ID: KB0087622
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | - |
| Not Applicable | - |
Description
Resolution:
GridServer 4.2 has the best scalability of any GridServer release to date. In our tests and in production environments, there are some configuration changes that can improve performance on large grids (> 1,000 engines). This will improve Manager performance in situations, for example, when the Broker Monitor response time may take several seconds to update. We strongly recommend upgrading to GridServer 4.2 in large grid environments.
For users of GridSever 4.1, the following changes can improve performance on large Grids:
* Increase the number of Resin request threads from the default of 200 to 300. A good rule of thumb is Resin Threads = Maximum Messaging Connections + Maximum Resource Download Connections + 50. This ensures enought threads to handle all messaging, downloads, and browser requests. To do this, edit the conf/resin.conf file at the top of the Broker's installation directory. Change the line that reads:
<thread-max>200</thread-max>
to change the setting to 300. Note that your Broker will restart when the resin.conf file is modified.
* On the Brokers, increase the Engine "Max Millis Per Heartbeat" value to be at least 2 minutes; the default is 30 seconds.
* Increase the SSL "Token Timeout," which is actually in effect regardless of SSL, for both the "Broker Resources" and "Director Resources" to be 5 minutes. The settings are on the Manager Configuration page, in the SSL section, under the Resource Deployment heading.
* Increase the Assignment Timeout, on the Manager Configuration page, in the Services section, to 60000 ms. Increasing this allows more time for an Engine to connect and pickup an assigned task when the Broker is under heavy load. This value should be increased if you see 'Task assignment expired:'… messages often.
* Separate the administrative port (web browser port) from the HTTP messaging port, to all administrative access even under heavy messaging load.
* On the Manager Configuration page, in the communication section, change Maximum Messaging Connections to 200; change Messaging Retry Wait to 10000 ms; change Maximum Resource Download Connections to 50; change Driver/Engine/Daemon Socket Timeout to 120 seconds.
* Increase the heap size. See KB article #8 - "The Manager runs out of memory" for details.
GridServer 4.2 has the best scalability of any GridServer release to date. In our tests and in production environments, there are some configuration changes that can improve performance on large grids (> 1,000 engines). This will improve Manager performance in situations, for example, when the Broker Monitor response time may take several seconds to update. We strongly recommend upgrading to GridServer 4.2 in large grid environments.
For users of GridSever 4.1, the following changes can improve performance on large Grids:
* Increase the number of Resin request threads from the default of 200 to 300. A good rule of thumb is Resin Threads = Maximum Messaging Connections + Maximum Resource Download Connections + 50. This ensures enought threads to handle all messaging, downloads, and browser requests. To do this, edit the conf/resin.conf file at the top of the Broker's installation directory. Change the line that reads:
<thread-max>200</thread-max>
to change the setting to 300. Note that your Broker will restart when the resin.conf file is modified.
* On the Brokers, increase the Engine "Max Millis Per Heartbeat" value to be at least 2 minutes; the default is 30 seconds.
* Increase the SSL "Token Timeout," which is actually in effect regardless of SSL, for both the "Broker Resources" and "Director Resources" to be 5 minutes. The settings are on the Manager Configuration page, in the SSL section, under the Resource Deployment heading.
* Increase the Assignment Timeout, on the Manager Configuration page, in the Services section, to 60000 ms. Increasing this allows more time for an Engine to connect and pickup an assigned task when the Broker is under heavy load. This value should be increased if you see 'Task assignment expired:'… messages often.
* Separate the administrative port (web browser port) from the HTTP messaging port, to all administrative access even under heavy messaging load.
* On the Manager Configuration page, in the communication section, change Maximum Messaging Connections to 200; change Messaging Retry Wait to 10000 ms; change Maximum Resource Download Connections to 50; change Driver/Engine/Daemon Socket Timeout to 120 seconds.
* Increase the heap size. See KB article #8 - "The Manager runs out of memory" for details.
Issue/Introduction
Large Grid configuration tips for better Manager performance (GridSever 4.1)
Feedback
Yes
No
Powered by
