On 06/18/2013 05:34 PM, Rajesh Khan wrote:
I currently have the following configuration and wanted to know if there was anything that I can do to boost the performance of my LVQ.Also there are some questions:The sender creates a LVQ with the following configuration "queue_name;{create:always, node:{type:queue, x-declare:{arguments:{'qpid.last_value_queue_key':'updates' , 'qpid.policy_type': ring, 'qpid.max_count': 0, 'qpid.max_size': 0}}}}";
It makes no sense to specify qpid.policy_type if you set qpid.max_count and qpid.max_size both to 0. I would remove all three options from your address for clarity. An LVQ will in any case be bounded by the number of distinct keys. (If the valid set of keys changes over time you will want to think about how and when old keys can be removed from the queue).
The sender has a capacity of 1500 Now The receiver is in browse mode and has a capacity of 5000 Here are some questions that I had 1)Will removing 'qpid.policy_type': ring, 'qpid.max_count': 0, 'qpid.max_size': 0 have any effect on the performance of the queue.
No, those have no effect since you are specifying no max depth (count and size are both 0). I would still remove them however, for the sake of clarity.
2)If I have multiple receivers on the same queue (both in browse mode) and in the same application will that make any difference. Wouldn't both go over the same messages.I dot see how having multiple receivers on browse mode make a difference on message consumption rate of a queue.
Yes, both will get the same messages. Adding another browser will certainly not speed up the first one. Are you sure you want an LVQ?
3)Any suggestions on what I could do to enhance the performance of the Queue/sender/Receiver?
What are you getting at present? Have you tried reducing receiver capacity a bit?
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
