On 04/25/2013 04:59 PM, SledgeHammer wrote:
I understand the concept of a queue :)... first in, first out... I also
understand that we have 7 or so message priorities to work with. However, my
situation is where a message represents a "job". So we can have a situation
where ProducerA will submit 100,000 jobs and then ProducerB will come along
and submit 4 or 5 jobs. As its set up right now, ProducerB will have to wait
for all 100,000 ProducerA jobs to get serviced before its 5 jobs get
serviced. What my boss wants to do is to defeat the whole point of a queue
and some how make it so that ProducerB doesn't have to wait for all 100,000
messages to be done. He kind of wants a sort of round robin picking from the
producers almost. I suggested to assign every message a random priority to
get an even distribution, but he complained that 14% (assuming 7 priorities)
of 100,000 is 14k. So ProducerB would have to wait for 14k messages...
Any ideas on how to interserse messages better?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Is-this-possible-with-ActiveMQ-tp4666219.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Might want to give this a read
http://www.christianposta.com/blog/?p=289
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
