Thank you for explanation. It clear now. In my case we dont want to keep no latency. Front end handles ( apache web-server) almost 14k-15k transactions per second and then we have java container ( weblogic) doing many things and one of them is connect to MQ ( a few are synchronous calls) . Weblogic uses MQ client and BINDING files to make the calls to MQ. Any latency anywhere means web-servers start choking up. We have web-servers limit setup to 18k. Any request beyond that is 500 error. MQ has been pretty stable .
Ensure your MQ Client interface is using some sort of connection pooling or is holding connections for use by multiple transactions. If the interface is putting to or getting from the same queue over multiple transactions, try to keep the queue open across multiple transactions.
Connection and Open Queue are the two most expensive operations in MQ. For best performance, avoid doing these as much as possible.
Thank you for sharing. I wasn't aware of this aspect of MQ client. I will explore more on this.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum