[
https://issues.apache.org/jira/browse/AMQ-6158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132431#comment-15132431
]
ASF subversion and git services commented on AMQ-6158:
------------------------------------------------------
Commit 25ff5699f1fb7c73668d5da2eacb53ad2ef14289 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=25ff569 ]
https://issues.apache.org/jira/browse/AMQ-6158
Computing messageSize for a durable subscription in KahaDB now runs much
faster (n vs n^2) which is noticable when there are a large number of
pending messages for a durable subscription.
> Computing message size for a durable subscription is very slow
> --------------------------------------------------------------
>
> Key: AMQ-6158
> URL: https://issues.apache.org/jira/browse/AMQ-6158
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, KahaDB
> Affects Versions: 5.13.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
>
> AMQ-5923 added a new feature to compute the pending message size for a
> durable subscription. The problem is that the current algorithm used in
> KahaDB to iterate over the pending messages for a subscription runs in O(n^2)
> because it uses the wrong index (location index) to compute the size.
> Now that AMQ-6097 has been resolved so that the order index contains size
> information for messages as well, we can rewrite the algorithm to be O\(n)
> which will make this run significantly faster for large pending message sizes
> (such as 100k messages, etc)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
