[
https://issues.apache.org/activemq/browse/AMQ-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49883#action_49883
]
Gary Tully commented on AMQ-2136:
---------------------------------
use of a transaction has an impact because a transaction boundary needs to be
accompanied with a disk write and disk sync. 5.1 did not honor the need to do a
disk sync on a transaction boundary and hence it is faster in this regard. 5.2
does the right thing.
Transactions will help if you do batch updates, but the overhead of transaction
demarcation is noticeable when there is a a small amount of activity (like one
message send or consume) in the transaction.
> Reply queue performance hit upgrading to 5.2
> --------------------------------------------
>
> Key: AMQ-2136
> URL: https://issues.apache.org/activemq/browse/AMQ-2136
> Project: ActiveMQ
> Issue Type: Bug
> Components: Performance Test
> Affects Versions: 5.2.0
> Environment: Windows Vista, JDK 1.6
> Reporter: H B
> Priority: Critical
> Attachments: test.java
>
>
> When upgrading to AMQ 5.2, my application gets 10x slower. This is traced to
> the usage of reply queue. I have written a test case (will be attached.)
> In 5.1,
> sender: 16.0 seconds spent for sending 8000 times, avg. 500.0msg/s
> In 5.2:
> sender: 432.0 seconds spent for sending 10000 times, avg. 23.148148msg/s
> I have tried arrange the steps a bit (see commented out line,) no help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
