[
https://issues.apache.org/jira/browse/HAMA-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196452#comment-15196452
]
ASF GitHub Bot commented on HAMA-987:
-------------------------------------
GitHub user lime62 opened a pull request:
https://github.com/apache/hama/pull/10
Fix issue HAMA-987
Changed netty transport for async communication from NIO to EPOLL.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lime62/hama HAMA-987
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hama/pull/10.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #10
----
commit 1dc5eaa2e5eeacb7ddc6571098a6c82117ec3745
Author: JongYoon Lim <[email protected]>
Date: 2016-03-15T23:12:31Z
Changed netty transport for async communication from NIO to EPOLL
----
> Netty native transport
> ----------------------
>
> Key: HAMA-987
> URL: https://issues.apache.org/jira/browse/HAMA-987
> Project: Hama
> Issue Type: Improvement
> Reporter: JongYoon Lim
> Priority: Minor
>
> This is a subtask of
> [HAMA-975|https://issues.apache.org/jira/browse/HAMA-975].
> Since 4.0.16, Netty provides the native socket transport for Linux using JNI.
> This transport has advantages as below.
> - higher performance
> - produces less garbage
> - edge-triggered
> - supports TCP-CORK
> So Hama will have better performance in async fashion communication.
> Full description for this can be found in [Netty
> Wiki|http://netty.io/wiki/native-transports.html]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
