[
https://issues.apache.org/jira/browse/ARTEMIS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573756#comment-16573756
]
ASF subversion and git services commented on ARTEMIS-1999:
----------------------------------------------------------
Commit 0b24d0b6925db0ad3458f077b087735b6087254a in activemq-artemis's branch
refs/heads/2.6.x from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=0b24d0b ]
ARTEMIS-1999 Broker uses 100% core's CPU time if msg grouping is used
The deliver loop won't give up trying to deliver messages when
back-pressure kicks in (credits and/or TCP) if msg grouping is used and
there are many consumers registered: this change will allow the loop
to exit by instructing the logic that the group consumer is the only
consumer to check.
(cherry picked from commit 8dd0e9472fc9eaf08c3d64c3935aeafbf04a422a)
> 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)
