You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2006/09/29 11:17:50 UTC
[jira] Created: (QPID-10) Broker throughput falls off with
transactions
Broker throughput falls off with transactions
---------------------------------------------
Key: QPID-10
URL: http://issues.apache.org/jira/browse/QPID-10
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Martin Ritchie
Assigned To: Martin Ritchie
When running the IBM PutGet test in transaction mode (-tx) throughput falls away.
Investigation is needed to see why the broker is getting bogged down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Created: (QPID-10) Broker throughput falls off with transactions
Posted by John O'Hara <jo...@gmail.com>.
How badly does it fall off?
One would expect throughput to be a lot lower if you're doing 1 TX per
message. About a third the performance.
If you do 1 TX for every 10 messages, performance should go up again.
If you do 1 TX for every 100 messages, performance will be faster for
persistent messages (get that!).
In real systems which care about persistence and guarantees, it is critical
to batch transactions to maintain throughput.
Its also critical to hold off writing to disk till the last possible moment
in the transaction to increase concurrency.
Try it with an RDBMS of your choice - its just a fact of life :-)
Cheers
John
On 29/09/06, Martin Ritchie (JIRA) <qp...@incubator.apache.org> wrote:
>
> Broker throughput falls off with transactions
> ---------------------------------------------
>
> Key: QPID-10
> URL: http://issues.apache.org/jira/browse/QPID-10
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Assigned To: Martin Ritchie
>
>
> When running the IBM PutGet test in transaction mode (-tx) throughput
> falls away.
>
> Investigation is needed to see why the broker is getting bogged down.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
[jira] Updated: (QPID-10) Broker throughput falls off with
transactions
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-10?page=all ]
Marnie McCormack updated QPID-10:
---------------------------------
Fix Version/s: M1
(was: M2)
> Broker throughput falls off with transactions
> ---------------------------------------------
>
> Key: QPID-10
> URL: http://issues.apache.org/jira/browse/QPID-10
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Fix For: M1
>
>
> When running the IBM PutGet test in transaction mode (-tx) throughput falls away.
> Investigation is needed to see why the broker is getting bogged down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (QPID-10) Broker throughput falls off with
transactions
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-10?page=all ]
Martin Ritchie resolved QPID-10.
--------------------------------
Resolution: Fixed
Assignee: (was: Martin Ritchie)
The problem was not on the broker. The client code created a new frameListener to block for a reply frame. However, this listener was never removed from the list when the reply frame arrived. As a result the list go massive and the listener's never gc'd. It is interesting that we never saw an out of memory exception. Only degradation in performance to due notification of a large list of listeners.
> Broker throughput falls off with transactions
> ---------------------------------------------
>
> Key: QPID-10
> URL: http://issues.apache.org/jira/browse/QPID-10
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
>
> When running the IBM PutGet test in transaction mode (-tx) throughput falls away.
> Investigation is needed to see why the broker is getting bogged down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-10) Broker throughput falls off with
transactions
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-10?page=all ]
Marnie McCormack updated QPID-10:
---------------------------------
Fix Version/s: M2
> Broker throughput falls off with transactions
> ---------------------------------------------
>
> Key: QPID-10
> URL: http://issues.apache.org/jira/browse/QPID-10
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Martin Ritchie
> Fix For: M2
>
>
> When running the IBM PutGet test in transaction mode (-tx) throughput falls away.
> Investigation is needed to see why the broker is getting bogged down.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira