activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-3188) Full table scan for durable subs in jdbc store when priority enabled; very slow with large message backlog
Date Tue, 22 Feb 2011 18:55:38 GMT

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

Gary Tully resolved AMQ-3188.
-----------------------------

    Resolution: Fixed

resolved in http://svn.apache.org/viewvc?rev=1073453&view=rev

query simplified such that full table scan is avoided. 

> Full table scan for durable subs in jdbc store when priority enabled; very slow with
large message backlog 
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3188
>                 URL: https://issues.apache.org/jira/browse/AMQ-3188
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 5.4.2
>         Environment: JDBC
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: DurableSubscriptions, JDBC,, Performance, Topic
>             Fix For: 5.5.0
>
>
> Priority support is delegate to the DB, but it currently requires a full table scan to
recover a new batch of messages. This can be very slow when the message table is large (a
consumer has been offline for some time). With multiple concurrent consumers this gets worse.
> The store needs to use more internal state w.r.t priority such that simpler/faster queries
are used.

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

        

Mime
View raw message