there is no relation between how fast a producer can send and how fast a consumer can receive. Lots of things effect performance, message type (persistant or not), acknowledge mode, paging, disc speed, network speed, memory etc etc. you decide on the gaurantees you want and configure accordingly and then tune your throughputvia flow control
Try using 2.3.0.Final. There was a big performance improvement on the Queues distribution.
It's hard to tell you also just by the description you gave (as Andy said). you probably can't have more than one consumer per subscription... which will possibly limit you. a Transaction needs to do a round trip and go through the disks if you are using persistency.
understood. 2 points:
- currenly I can't upgrade to 2.3.0.Final as AFAIK it is not backward compatible.
- Consumer running on the same machine we get 3K but on a separate machine 1.5K – why is the network latency causing a drop in TPS?