Yes this is exactly the advantage I was thinking of. If we pursue this
we'll test it and I'll report back for posterity.
On Tue, Jul 28, 2020, 1:35 PM Justin Bertram wrote:
> My advice would simply be to test your use-cases. I don't think anybody can
> say with confidence exactly what you're goi
My advice would simply be to test your use-cases. I don't think anybody can
say with confidence exactly what you're going to find. The overhead of
addresses and queues certainly isn't zero.
I would add that one potential benefit of multiple addresses & queues would
have over a single address/queue
Take a look to https://github.com/apache/activemq-artemis/pull/3217 if your
use case involve auto creating many queues that's the kind of issues you
can hit, check the referenced Jira
Hope it helps,
Franz
Il dom 26 lug 2020, 16:52 Alec Henninger ha
scritto:
> Right, succinctly the scenario is:
Right, succinctly the scenario is:
* Relatively low rate from message producer
* Very high possible number of addresses (though could be pruned with
TTL/auto deletion to your point; that is, only few should actually have
messages most of the time)
* Even higher number of queues (multiple consumers
Hi Alex,
I'm not one of the maintainers and maybe they will respond.
To clarify, are you asking whether routing high volumes of messages though
a large number of addresses is likely to lead to poor performance versus
using a small number of addresses?
I can't answer that but Artemis was designed
I was using addresses and queues interchangeably. It's been a minute since
I looked at the artemis address module and I realize now they shouldn't be
mixed up. I think the question is about both, since there would be many
addresses–let's assume all multicast–and then each may get many consumers,
cr
Hello,
I'm wondering about the overhead of queues (addresses) in Artemis.
Thinking about ordering messages, we can use groups. But queues (with a
single consumer) are already ordered. Could we instead use many individual
queues?
Message groups are (at least given the documentation example) suita
