You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Todd Lipcon (Commented) (JIRA)" <ji...@apache.org> on 2012/02/14 05:13:00 UTC
[jira] [Commented] (HADOOP-8069) Enable TCP_NODELAY by default for
IPC
[ https://issues.apache.org/jira/browse/HADOOP-8069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207491#comment-13207491 ]
Todd Lipcon commented on HADOOP-8069:
-------------------------------------
A good reason to do this is that, when I run an IPC benchmark on an "echo" function, as soon as the message size eclipses 8K the latency goes up to 40ms due to the interaction of nagling and delayed ACK.
> Enable TCP_NODELAY by default for IPC
> -------------------------------------
>
> Key: HADOOP-8069
> URL: https://issues.apache.org/jira/browse/HADOOP-8069
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> I think we should switch the default for the IPC client and server NODELAY options to true. As wikipedia says:
> {quote}
> In general, since Nagle's algorithm is only a defense against careless applications, it will not benefit a carefully written application that takes proper care of buffering; the algorithm has either no effect, or negative effect on the application.
> {quote}
> Since our IPC layer is well contained and does its own buffering, we shouldn't be careless.
--
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