You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/07/18 05:30:04 UTC
[jira] Created: (DIRMINA-403) Performance degradation when socket
receive buffer is big.
Performance degradation when socket receive buffer is big.
----------------------------------------------------------
Key: DIRMINA-403
URL: https://issues.apache.org/jira/browse/DIRMINA-403
Project: MINA
Issue Type: Bug
Components: Transport
Affects Versions: 1.1.0, 1.0.3
Reporter: Trustin Lee
Assignee: Trustin Lee
Priority: Minor
Fix For: 1.0.4, 1.1.1
SocketIoProcessor always allocates a buffer whose size is same with the socket receive buffer size, which is often very big (e.g. 40kb). Because the buffer is allocated for every read operation, the buffer allocation can often be a bottleneck because most applications don't fill the socket receive buffer that much.
One solution is to dynamically adjust the size of the read buffer instead of using the socket receive buffer size value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRMINA-403) Performance degradation when socket
receive buffer is big.
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trustin Lee closed DIRMINA-403.
-------------------------------
Resolution: Fixed
Fixed using the following algorithm.
http://tinyurl.com/3bc8wo
> Performance degradation when socket receive buffer is big.
> ----------------------------------------------------------
>
> Key: DIRMINA-403
> URL: https://issues.apache.org/jira/browse/DIRMINA-403
> Project: MINA
> Issue Type: Bug
> Components: Transport
> Affects Versions: 1.0.3, 1.1.0
> Reporter: Trustin Lee
> Assignee: Trustin Lee
> Priority: Minor
> Fix For: 1.0.4, 1.1.1
>
>
> SocketIoProcessor always allocates a buffer whose size is same with the socket receive buffer size, which is often very big (e.g. 40kb). Because the buffer is allocated for every read operation, the buffer allocation can often be a bottleneck because most applications don't fill the socket receive buffer that much.
> One solution is to dynamically adjust the size of the read buffer instead of using the socket receive buffer size value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.