[jira] [Resolved] (AMQ-3397) Improve scalability of active durable subs with JDBC message store

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3397.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/viewvc?rev=1144340&view=rev

Added a cache to topic message store of the store sequence ids to avoid each ack going to the store twice.
A nice boost in throughput for active durable subs; 100 subs, 550->2200 for 2min test with mysql

That sequenceid has been there for a while to ensure message order with overlapping transactions but the overhead for muiltiple durable subs was excessive.

> Improve scalability of active durable subs with JDBC message store
> ------------------------------------------------------------------
>
>                 Key: AMQ-3397
>                 URL: https://issues.apache.org/jira/browse/AMQ-3397
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 5.5.0
>         Environment: jdbc store
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: durable, jdbc, scaleability, topic
>             Fix For: 5.6.0
>
>
> With 1 producer, scaling from 1 to 100 durable subs, the through put drops off significantly. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira