This content has been marked as final.
Show 4 replies
-
1. Re: What is holding back a consumer?
ataylor Apr 25, 2013 10:32 AM (in response to yairogen)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
-
2. Re: What is holding back a consumer?
clebert.suconic Apr 25, 2013 12:16 PM (in response to yairogen)Try using 2.3.0.Final. There was a big performance improvement on the Queues distribution.
-
3. Re: What is holding back a consumer?
clebert.suconic Apr 25, 2013 12:18 PM (in response to yairogen)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.
-
4. Re: What is holding back a consumer?
yairogen Apr 27, 2013 3:23 PM (in response to clebert.suconic)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?
Thanks