On Monday 31 July 2006 22:04, Akatemik wrote: > I'm running the basic django server and everything works fine from lan. > But from outside every request has a three second overhead, even if > it's just a 304. This means that a small html-page with three JS-files > and a stylesheet takes 15 seconds to load. > > With apache everything works fine even from wan. I also did tcpdumps at > my external and internal interfaces on my firewall, which show that the > packets aren't delayed by the fw by no more than 0.1ms. They also show > that the ack for the GET is returned almost instantly but the http > payload doesn't begin to send until about three seconds later (at least > according to my limited knowledge of ethereal). Once the sending > starts, it's all finished in milliseconds and the next lag occurs when > the client GETs another file. > > Any idea what could be happening? It's making development testing quite > hard, since all my volunteer testers get fed up with waiting for > pageloads.
In my experience, when you encounter non-obvious but fairly consistant slow downs in net traffic, the first thing to check is DNS. In this case, I'd make sure that each of the DNS cache servers that the client consults to resolve the address of your server can perform both a forward and reverse lookup of your server's name an IP. Conversely, make sure the server isn't being slowed down by failed attempts at reverse lookups on the client. HTH, John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
