MQSeries.net :: View topic - Subscriber over WAN

jljunk · Posted: Fri Mar 22, 2013 9:09 am Post subject:

Got a broker queue with a single client subscriber app.
Client and Broker are separated across the WAN.

Client is Java and we're using JMS.

What if anything can we do to improve the consumption rate by the consumer ie client throughput.
We cannot influence the size of the messages arriving at the broker from the publisher as we are not in control of the app publishing to the queue.

We are seeing that the avg time to consume a single message is approximately the round tip time of the network.
We interpret this to mean that each message consumption does a round trip to the broker - same results in async and sync modes.

Does MQ support any optimisation options for slow networks?
I understand that some messaging products have an prefetch so that a single client side consume actually pulls a block of messages across the wire from the broker so that the round trips are reduced. Essentially a form of pipelining.

One option we have considered is putting a proxy closer to the broker and have it provide the batching/prefetch for us and possibly use a different protocol between the proxy and the client if necessary.
We would rather stay all MQ if possible - not least because this approach means more hardware and monitoring etc.

Thoughput is important to us not latency per message.

?? Is it possible to configure the broker to repackage blocks of messages in its queue into a bigger less granular package? Its the RTT that's the biggest killer for us. Less RT = better throughput.

Advice appreciated.