DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42871>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42871

           Summary: Performance with proxy connections (missing TCP_NODELAY)
           Product: Apache httpd-2
           Version: 2.2.4
          Platform: Other
        OS/Version: AIX
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_proxy
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


While running performance testes, we have run into an issue when an Apache web 
server is set in front of a tomcat (ajp in between).

When POST http requests were forwarded, we were experiencing the following 
network sequence:
- a first ajp packet containing headers/request was forwarded by Web server to 
tomcat: body data aren't included in it
- Web server would wait for tomcat server to send back an TCP/IP ACK
- Web server would then send the second ajp packet containing the POST body 
data
=> TCP/IP ACK can take as much as 150ms to be sent (Naggle algorithm)
=> if tomcat app needs to process post data, it will block this amount of time 
before being able to process it

In proxy_util.c, sockets being created do not have the TCP_NODELAY option set: 
i have patched the module and performed testes again. Now, web server no 
longer waits for the tomcat ack to be sent and post data are sent immediately 
after the first packet. Response time have then been lowered.

I will attach the patch to proxy_util.c: it applies to non ftp proxy 
connections. For ftp, i have found that mod_proxy_ftp.c opens its own sockets 
and would require a similar patch not provided here.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to