You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/06/27 23:05:45 UTC
[jira] [Created] (AMQNET-391) Add buffered stream in TcpTransport
to avoid excessive packet transmision
Timothy Bish created AMQNET-391:
-----------------------------------
Summary: Add buffered stream in TcpTransport to avoid excessive packet transmision
Key: AMQNET-391
URL: https://issues.apache.org/jira/browse/AMQNET-391
Project: ActiveMQ .Net
Issue Type: Improvement
Components: ActiveMQ
Affects Versions: 1.5.5
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Minor
Fix For: 1.5.6, 1.6.0
Currently the TcpTransport utilizes a raw NetworkStream which is okay when loosmarshalling is enabled and size prefix is turned on but when either of those is not true the marshaling code writes directly to the stream and can result in a lot of small Tcp packets getting transmitted for each message instead of one larger more efficient write.
--
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
[jira] [Commented] (AMQNET-391) Add buffered stream in TcpTransport
to avoid excessive packet transmision
Posted by "Brian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411220#comment-13411220 ]
Brian commented on AMQNET-391:
------------------------------
Extra packets are still being generated when stream becomes larger than the buffer of BufferedStream. The default buffer size is 4096 bytes so sending a stream greater than 4096 bytes results in 1 or more additional packets compared to when tight encoding is disabled.
> Add buffered stream in TcpTransport to avoid excessive packet transmision
> -------------------------------------------------------------------------
>
> Key: AMQNET-391
> URL: https://issues.apache.org/jira/browse/AMQNET-391
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.5.5
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.5.6, 1.6.0
>
>
> Currently the TcpTransport utilizes a raw NetworkStream which is okay when loosmarshalling is enabled and size prefix is turned on but when either of those is not true the marshaling code writes directly to the stream and can result in a lot of small Tcp packets getting transmitted for each message instead of one larger more efficient write.
--
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
[jira] [Commented] (AMQNET-391) Add buffered stream in TcpTransport
to avoid excessive packet transmision
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432229#comment-13432229 ]
Timothy Bish commented on AMQNET-391:
-------------------------------------
Enhancements on trunk will allow this to be configured in v1.6 using the send / receive buffer sizes.
> Add buffered stream in TcpTransport to avoid excessive packet transmision
> -------------------------------------------------------------------------
>
> Key: AMQNET-391
> URL: https://issues.apache.org/jira/browse/AMQNET-391
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.5.5
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.5.6, 1.6.0
>
>
> Currently the TcpTransport utilizes a raw NetworkStream which is okay when loosmarshalling is enabled and size prefix is turned on but when either of those is not true the marshaling code writes directly to the stream and can result in a lot of small Tcp packets getting transmitted for each message instead of one larger more efficient write.
--
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
[jira] [Comment Edited] (AMQNET-391) Add buffered stream in
TcpTransport to avoid excessive packet transmision
Posted by "Brian (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411220#comment-13411220 ]
Brian edited comment on AMQNET-391 at 7/11/12 12:25 PM:
--------------------------------------------------------
Extra packets are still being generated when stream becomes larger than the buffer of BufferedStream. The default buffer size is 4096 bytes so sending a stream greater than 4096 bytes results in 1 or more additional packets compared to when tight encoding is disabled.
If 2 extra packets are generated, the total bytes sent when tight encoding is enabled becomes larger than not using tight encoding.
was (Author: pebrian27):
Extra packets are still being generated when stream becomes larger than the buffer of BufferedStream. The default buffer size is 4096 bytes so sending a stream greater than 4096 bytes results in 1 or more additional packets compared to when tight encoding is disabled.
> Add buffered stream in TcpTransport to avoid excessive packet transmision
> -------------------------------------------------------------------------
>
> Key: AMQNET-391
> URL: https://issues.apache.org/jira/browse/AMQNET-391
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.5.5
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.5.6, 1.6.0
>
>
> Currently the TcpTransport utilizes a raw NetworkStream which is okay when loosmarshalling is enabled and size prefix is turned on but when either of those is not true the marshaling code writes directly to the stream and can result in a lot of small Tcp packets getting transmitted for each message instead of one larger more efficient write.
--
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
[jira] [Resolved] (AMQNET-391) Add buffered stream in TcpTransport
to avoid excessive packet transmision
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-391.
---------------------------------
Resolution: Fixed
Fixed in trunk and the 1.5.x branch
> Add buffered stream in TcpTransport to avoid excessive packet transmision
> -------------------------------------------------------------------------
>
> Key: AMQNET-391
> URL: https://issues.apache.org/jira/browse/AMQNET-391
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.5.5
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.5.6, 1.6.0
>
>
> Currently the TcpTransport utilizes a raw NetworkStream which is okay when loosmarshalling is enabled and size prefix is turned on but when either of those is not true the marshaling code writes directly to the stream and can result in a lot of small Tcp packets getting transmitted for each message instead of one larger more efficient write.
--
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