[ http://issues.apache.org/jira/browse/AXISCPP-749?page=all ]
John Hawkins updated AXISCPP-749:
---------------------------------
Priority: Trivial (was: Major)
This is a "nice-to-have" so making it "trivial"
> Currently TCP_NODELAY is turned off. This is only efficient when the
> messages are small.
> -----------------------------------------------------------------------------------------
>
> Key: AXISCPP-749
> URL: http://issues.apache.org/jira/browse/AXISCPP-749
> Project: Axis-C++
> Type: Improvement
> Components: Transport (axis3), Transport (Client)
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
