On Wed, 2006-08-02 at 14:01 +0000, DavidA wrote: > > Akatemik wrote: > > > 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. > > > > You are correct, if I add the client machine to /etc/hosts on django > > server, everything is smooth. However I find quite odd that the server > > does a separate reverse dns checks for every GET it gets even in the > > same connection... > > Turn this off in your Apache httpd.conf with: > > HostnameLookups off > > It was defaulted to on in older versions of Apache to make the logs > more readable but impacts performance (as you well know).
Um, Dave? The original poster was using the development server. Apache doesn't get a seat at the table here. :-) Cheers, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
