You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Created) (JIRA)" <ji...@apache.org> on 2011/11/11 11:06:51 UTC
[jira] [Created] (QPID-3610) set TCP_NODELAY true by default in the
Java client to improve general performance
set TCP_NODELAY true by default in the Java client to improve general performance
---------------------------------------------------------------------------------
Key: QPID-3610
URL: https://issues.apache.org/jira/browse/QPID-3610
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: 0.14
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
Fix For: 0.15
set TCP_NODELAY true by default in the Java client to improve general performance.
TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3610) set TCP_NODELAY true by default in
the Java client to improve general performance
Posted by "Rajith Attapattu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148519#comment-13148519 ]
Rajith Attapattu commented on QPID-3610:
----------------------------------------
I was thinking about including something in the Programming with Apache Qpid doc.
This is probably something worth mentioning explicitly to avoid any confusion.
What do you think ?
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3610) set TCP_NODELAY true by default in
the Java client to improve general performance
Posted by "Robbie Gemmell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148518#comment-13148518 ]
Robbie Gemmell commented on QPID-3610:
--------------------------------------
I considered the JIRA title and description sufficient? Do we have documentation that it is false by default that I need top update?
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3610) set TCP_NODELAY true by default in
the Java client to improve general performance
Posted by "Rajith Attapattu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148507#comment-13148507 ]
Rajith Attapattu commented on QPID-3610:
----------------------------------------
Robbie, lets make sure we document the change in default.
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Resolved] (QPID-3610) set TCP_NODELAY true by default in
the Java client to improve general performance
Posted by "Robbie Gemmell (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3610.
----------------------------------
Resolution: Fixed
Update applied
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3610) set TCP_NODELAY true by default in the
Java client to improve general performance
Posted by "Robbie Gemmell (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-3610:
---------------------------------
Affects Version/s: (was: 0.14)
0.12
Fix Version/s: (was: 0.15)
0.14
Merged to 0.14 branch.
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.12
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.14
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3610) set TCP_NODELAY true by default in
the Java client to improve general performance
Posted by "Robbie Gemmell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148525#comment-13148525 ]
Robbie Gemmell commented on QPID-3610:
--------------------------------------
Seems reasonable, I will take a look over the weekend and see where I can slot something in about it.
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3610) set TCP_NODELAY true by default in
the Java client to improve general performance
Posted by "Justin Ross (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148576#comment-13148576 ]
Justin Ross commented on QPID-3610:
-----------------------------------
Reviewed and approved for 0.14.
> set TCP_NODELAY true by default in the Java client to improve general performance
> ---------------------------------------------------------------------------------
>
> Key: QPID-3610
> URL: https://issues.apache.org/jira/browse/QPID-3610
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> set TCP_NODELAY true by default in the Java client to improve general performance.
> TCP_NODELAY is currently set false by default. This leads to synchronous commands such as ExecutionSync or TxCommit taking a potentially very long amount of time (~30-40ms observed), which cripples transactional performance, causes consumer creation to take a long time, and generally impedes performance of messaging patterns such as request-response.
> Whilst this change could perhaps cause some falloff in out-the-box peak throughput in situations such as NoAck mode, the observed performance increases in a variety of other situations such as the above is too large (anything from 10% to 1000%, yes 10x throughput, has been observed in select tests) to ignore for our general out-the-box configuration. Users interested in the ultimate throughput will be the ones most likely to tune for it, so we should set default configuration to cater for those who arent/dont.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org