[#MB-1140] Broker performance does not scale with multiple consumers when using JDBC persistence adapter.

FUSE Message Broker

Broker performance does not scale with multiple consumers when using JDBC persistence adapter.

Created: 13/Apr/12 03:14 PM Updated: 17/Jul/12 07:29 AM

Component/s:

broker

Affects Version/s:

5.5.1-fuse-03-06

Fix Version/s:

5.5.1-fuse-07-11

Environment:

JDBC persistence adapter

External Issue URL:

https://issues.apache.org/jira/browse/AMQ-2868

Description

« Hide

The brokers throughput should scale with multiple concurrent consumers connected. This is the case when kahadb is used as the persistence adapter but its not the case when running the broker with the JDBC persistence adapter.
The JDBC persistence adapter should be improved to scale similarly to KahaDB.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Dejan Bosanac added a comment - 01/Jun/12 10:45 AM

We removed synchronization on commit in the transaction store used by JDBC, as it is not needed any more. This should improve performances of this use case (all the tests indicate so). The snapshot with this change (20120601.101605-21) is available at

http://repo.fusesource.com/nexus/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.5.1.fuse-SNAPSHOT/