You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "nadir amra (JIRA)" <ax...@ws.apache.org> on 2008/01/19 01:44:34 UTC

[jira] Closed: (AXISCPP-749) Currently TCP_NODELAY is turned off. This is only efficient when the messages are small.

     [ https://issues.apache.org/jira/browse/AXISCPP-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nadir amra closed AXISCPP-749.
------------------------------

    Resolution: Won't Fix

Since the current implementation writes out 2 buffers, one for the header and one for the SOAP message, I see no reason to do anything with this at this time.  

> Currently TCP_NODELAY is turned off.  This is only efficient when the messages are small.
> -----------------------------------------------------------------------------------------
>
>                 Key: AXISCPP-749
>                 URL: https://issues.apache.org/jira/browse/AXISCPP-749
>             Project: Axis-C++
>          Issue Type: Improvement
>          Components: Transport (axis3), Transport (Client)
>    Affects Versions: current (nightly)
>         Environment: n/a
>            Reporter: Fred Preston
>            Priority: Trivial
>
> When setting up the socket, the following initialisation is performed (see the last few lines of method HTTPChannel::OpenChannel() and HTTPSSLChannel::OpenChannel())...
>     /* Turn off the Nagle algorithm - Patch by Steve Hardy */
>     /* This is needed, because our TCP stack would otherwise wait at most
>      * 200 ms before actually sending data to the server (while waiting for
>      * a full packet). This limits performance to around 5 requests per
>      * second, which is not acceptable. Turning off the Nagle algorithm
>      * allows for much faster transmission of small packets, but may
>      * degrade high-bandwidth transmissions.
>      */
>     int one = 1;
>     setsockopt( m_Sock, IPPROTO_TCP, TCP_NODELAY, (char *) &one, sizeof( int));
> When the message is not so small, does this omission degrade the socket performance?  Would it be better to set a threshold and perhaps change the socket options 'on the fly' when the message size dictates that it should be handled differently?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org