Why does the performance of EMS server goes down significantly, when a maxbytes is set for a destination and the maxbytes limit for the destination has exceeded?
Article ID: KB0091691
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
If the EMS server log file/console trace has DEFAULT parameters (including LIMITS), the performance of the EMS server will be significantly low, as for each message being pushed to the destination, the EMS server has to write “limit exceeded” to the EMS server logs and console. As disk I/O is significantly slow than in memory operations, the performance (out going message rate) of the EMS server will go down.
If you remove the “LIMITS” parameter from the console trace and the log trace, performance will increase a lot.
If the EMS server log file/console trace has DEFAULT parameters (including LIMITS), the performance of the EMS server will be significantly low, as for each message being pushed to the destination, the EMS server has to write “limit exceeded” to the EMS server logs and console. As disk I/O is significantly slow than in memory operations, the performance (out going message rate) of the EMS server will go down.
If you remove the “LIMITS” parameter from the console trace and the log trace, performance will increase a lot.
Issue/Introduction
Why does the performance of EMS server goes down significantly, when a maxbytes is set for a destination and the maxbytes limit for the destination has exceeded?
Feedback
Yes
No
Powered by
