[jira] [Comment Edited] (AMQ-3557) Performance of consumption with JDBC persistance and Microsoft SQL Server

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

    [ https://issues.apache.org/jira/browse/AMQ-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13441176#comment-13441176 ] 

Gary Tully edited comment on AMQ-3557 at 11/8/17 4:58 PM:
----------------------------------------------------------

The jdbc version of test: org.apache.activemq.usecases.DurableSubscriptionSelectorTest#testSubscription 
demonstrates the need to setMaxRows to a large value in the sparse selector case. Using a large destination page size via policy is a better solution as it is more specific.


was (Author: gtully):
The jdbc version of test: org.apache.activemq.usecases.DurableSubscriptionSelectorTest#testSubscription 
demonstrates the need to setMaxRows to a large value in the sparse selector case. Using a large destination page size via polity is a better solution as it is more specific.

> Performance of consumption with JDBC persistance and Microsoft SQL Server
> -------------------------------------------------------------------------
>
>                 Key: AMQ-3557
>                 URL: https://issues.apache.org/jira/browse/AMQ-3557
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store, Performance Test
>    Affects Versions: 5.4.3, 5.5.0, 5.5.1
>         Environment: Microsoft SQL Server 2005, Debian Linux, 
>            Reporter: Nicholas Rahn
>              Labels: jdbc, performance, sqlserver
>             Fix For: 5.7.0
>
>         Attachments: activemq.xml
>
>
> We are trying to upgrade our ActiveMQ installation and have run into some performance issues. I'll attached our activemq.xml file to this bug.
> I've setup a fresh SQLServer database for our upgrade tests and using the example Ant tools in the distribution, I've populated a persistent queue with 1,000,000 messages. I then consume those messages using the example Ant consumption script. The producing side works fine. However the performance of the consumption side is extremely poor. To consume just 10,000 of those messages takes over 5 minutes.
> The consumer will pause for 4-5 seconds every 200 messages. This is easily visible in the output of the Ant script. We have also traced the DB to see what is happening there and have found that the findNextMessagesStatement takes 4-5 seconds every time it is executed. The statement's ID parameter is increased by 200 every time it is executed.  We also noticed the use of the "SET ROWCOUNT 10000" statement setting the maximum number of rows returned from a query at 10000. We also traced previous versions of ActiveMQ and found that SET ROWCOUNT was used much more often, with much smaller values (often 10, 20 or 30).
> We have also tested the same setup with version 5.4.0 and did not have the same issues. Consumption speeds with 5.4.0 were normal, with no pauses. Version 5.4.3 did have the problem, however. So there seems to be a regression somewhere between 5.4.0 and 5.4.3 (also affects 5.5.0 and later).
> Please let me know if you need more information, including the database traces.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)