You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/08/09 19:30:20 UTC
[jira] [Comment Edited] (AMQ-6390) Performance issue when selecting
messages
[ https://issues.apache.org/jira/browse/AMQ-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414095#comment-15414095 ]
Christopher L. Shannon edited comment on AMQ-6390 at 8/9/16 7:30 PM:
---------------------------------------------------------------------
You might want to try hooking up a profiler to the server JVM and see what method calls the JVM is spending most of its time in to pinpoint exactly where the performance is slow.
was (Author: christopher.l.shannon):
You might want to try hooking up a profiler to the server JVM and see what method calls the JVM is spending most of its time to pinpoint exactly where the performance is slow.
> Performance issue when selecting messages
> -----------------------------------------
>
> Key: AMQ-6390
> URL: https://issues.apache.org/jira/browse/AMQ-6390
> Project: ActiveMQ
> Issue Type: Bug
> Components: Selector, Transport
> Affects Versions: 5.13.2
> Reporter: Matt Ho
>
> Here is the scenario:
> 1. Start a standalone activemq server (memory persistence)
> 2. Enqueue 3000+ message to a queue
> 3. Dequeue by message selector, and the performance is REALLY bad.
> It seems like MessageConsumer is waiting MessageDispatchChannel to get all the messages from server. Can you fix it in the following updates?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)