How to improve the performance of concurrent EMS SSL connections and re-connections.
book
Article ID: KB0092462
calendar_today
Updated On:
Products
Versions
TIBCO Enterprise Message Service
-
Not Applicable
-
Description
Description: How to improve the performance of concurrent EMS SSL connections and re-connections. Symptoms: When many EMS SSL connections and reconnections happen concurrently,
the EMS server may report the warning message: "Closing SSL
connection from *** due to timeout.“. It may take a longer time to
establish SSL connections and re-connections. How to improve the performance? Cause: EMS handles SSL connection handshakes synchronously within one network
I/O thread. It is expected that some delay may happen when multiple SSL
connections were created at the same time.
Issue/Introduction
How to improve the performance of concurrent EMS SSL connections and re-connections.
Resolution
Beginning with EMS 7.0, two new parameters were introduced that allow you to fine-tune performance on multi-core machines:
- To bind network I/O threads to specific processors, set the processor_ids parameter in the tibemsd.conf.
- To bind a storage thread to a specific processor, set processor_id in the stores.conf file.
These
parameters are supported on Linux, Solaris and Windows platforms.
Since EMS 8.1.0, we introduced the network_thread_count server property which is supported on all platforms. The EMS server ignores this parameter if the processor_ids parameter is also specified. Check the EMS user guide for details regarding these new parameters.
When you configure multiple network I/O threads based on specific processors, it can improve the performance of concurrent SSL connections to the EMS server to a certain degree. You need to run through performance tests to select the best value for this parameter in your production environment.