[
https://issues.apache.org/jira/browse/ARTEMIS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563791#comment-16563791
]
ASF GitHub Bot commented on ARTEMIS-1999:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2203
> exclusive yes i think would have similar issue, after all it followed
the same logic of message groups in part. It would be easy to fix, as in the
same place / if statement just check for the exclusive flag.
Nice, I suppose that would be better to raise a different issue/PR for that
even if I'm tempted to do it fro this one: it is indeed fixing a similar but
different issue.
I'm anyway opened to do it differently too :+1:
> what if all consumers are busy and a message group isnt assigned? it
would still spin i assume.
I the message group isn't assigned it will use round robin between the
consumers until noDeliver == size: in that case it will stop spinning without
burning any CPU, because deliverAsync won't be called anymore.
> Broker is using 100% core's CPU time if message grouping is used
> ----------------------------------------------------------------
>
> Key: ARTEMIS-1999
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1999
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.6.2
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Fix For: 2.6.3
>
> Attachments: cpu.svg
>
>
> When consuming messages with message grouping set on the broker seem to
> consume excessive amount of CPU time. On 12 core CPU it can be observed that
> one core goes 100% and stays that way as long as there is more than one
> consumer attached to a queue. Once the number of consumers is reduced to 1
> the CPU usage goes to normal. But moment another consumer is attached another
> CPU core goes 100%.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
