Tracd HTTP response is very slow in windows between PCs.

[JoneyWu@…]

When I installed the trac in standalone way, I found it is very slow to response to browser. But this case only appear in connection from another PC. It means if I access the trac in the local machine, the speed is normal (about 0.0x seconds). I have traced the Trac code and found that: it is fine with good speed in handling the request but stuck in "send_response" step. This situation will add extra 12 seconds cost to response to the browser. Maybe is the IO/Network issue?

e.g. from my trac log— "19:45:49 Trac[standalone] DEBUG: Total request time: 12.032000 s"

[Christian Boos]

The standard python HTTPServer used by TracStandalone will log each client request. While doing this, it tries to resolve the client's numerical IP address to a fully qualified name. You probably don't have a DNS server correctly setup in your environment, hence the slow down.

So either fix that (preferred solution) or, if it's not an option, apply the following patch (hack):

Index: trac/web/standalone.py
===================================================================
--- trac/web/standalone.py	(revision 3387)
+++ trac/web/standalone.py	(working copy)
@@ -249,6 +249,16 @@
         self.wfile = None
         self.rfile = None
 
+    def address_string(self):
+        """Return the client address formatted for logging.
+
+        This version doesn't look up the full hostname using
+        gethostbyaddr() ...
+        """
+
+        host, port = self.client_address[:2]
+        return host
+
     def do_POST(self):
         self._do_trac_req()
 

(patch on stable, something similar could be done on trunk; the method is added to the TracHTTPRequestHandler class)

[caoyanlong@…]

Trac 0.10 release has same issue.

env:

os: windows 2003 & sp1 python: 2.4.3 standalone mode, tracd -s -d -a…

Browse it in local host will be very quick as my old trac 0.9.5. But it will very very slow from another PC in 100M LAN. It costs >60s!

[anonymous]

In version 0.10, the following patch does the trick to disable dns reverse lookups (against trac/web/wsgi.py):

—- orig/wsgi.py 2006-11-06 10:36:11.991122600 -0700 +++ wsgi.py 2006-11-06 10:35:16.820306900 -0700 @@ -121,6 +121,9 @@

class WSGIRequestHandler(BaseHTTPRequestHandler):

+ def address_string(self): + host, port = self.client_address[:2] + return host

def setup_environ(self):

self.raw_requestline = self.rfile.readline()

[caoyanlong@…]

thanks a lot. It is ok!

[Emmanuel Blot]

(no change committed to the Trac base code)

[Christopher Lenz]

Replying to eblot:

(no change committed to the Trac base code)

… meaning this issue is still open!

[Christopher Lenz]

Oops, I missed Christians response to this :-P

In any case, I think we should disable reverse lookups in tracd to get rid of this problem. I don't see any value in reverse lookups and pretty much every web server I know has them disabled by default. Plus, tracd is meant for being run either for development, or behind a HTTP proxy.

[Christian Boos]

Well, I'm all for disabling reverse lookups there, choose your patch ;)

[Christopher Lenz]

Fixed in [4161].