How will EMS behave with high number of connections?
Article ID: KB0087350
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
We cannot provide benchmarks, because performances can be impacted by too many variables,
Throughput performance is affected by a number of factors including:
1. Message size
2. Number of clients
3. Bandwidth
4. Processor and NIC card performance
5. If message selectors are used.
6. If tracing and/or statistics is enabled
7. Message delivery mode
8. Acknowledgment mode
9. Implementation of OS
10. Expiration time
11. Authorization
12. Route/bridge
13. Transactions
.... and many other factors.
As the actual throughput is determined by many factors as mentioned above,
the best benchmark is the one that you run tests in your own environment,
with the hardware that you plan to use and the message flow and characteristics
that you plan to use in production.
We provide customers with two sample programs "tibjmsMsgProducerPerf.java and tibjmsMsgConsumerPerf.java
(located in the <EMS_INSTALL>/samples/java directory) which can be used to
generate messages with multiple threads and connections. You can use these samples
to simulate topic, queue, messages size, threads, delivery mode ....
Alternatively, customers may consult our PSG Architect for the EMS applications to improve their application performance, and analyse like the complexity/scale of your scenario.
We cannot provide benchmarks, because performances can be impacted by too many variables,
Throughput performance is affected by a number of factors including:
1. Message size
2. Number of clients
3. Bandwidth
4. Processor and NIC card performance
5. If message selectors are used.
6. If tracing and/or statistics is enabled
7. Message delivery mode
8. Acknowledgment mode
9. Implementation of OS
10. Expiration time
11. Authorization
12. Route/bridge
13. Transactions
.... and many other factors.
As the actual throughput is determined by many factors as mentioned above,
the best benchmark is the one that you run tests in your own environment,
with the hardware that you plan to use and the message flow and characteristics
that you plan to use in production.
We provide customers with two sample programs "tibjmsMsgProducerPerf.java and tibjmsMsgConsumerPerf.java
(located in the <EMS_INSTALL>/samples/java directory) which can be used to
generate messages with multiple threads and connections. You can use these samples
to simulate topic, queue, messages size, threads, delivery mode ....
Alternatively, customers may consult our PSG Architect for the EMS applications to improve their application performance, and analyse like the complexity/scale of your scenario.
Issue/Introduction
How will EMS behave with high number of connections?
Feedback
Yes
No
Powered by
