It could have to with a lot of stuff. It is possible that FF has some DNS cache that gets flushed , it also almost certain ( don't trust me, my ISP has, I guess it is common :) ) that your ISP has a DNS cache and it is possible that other users queries have flushed yours. You can ask mozilla-devs and your ISP , however this won't help for users of other ISPs and other browsers :) You are tweaking the server , right ? So , place a machine as close to it as possible ( put a second lan-card in the server , and connect the two machines) , alias the server in /etc/hosts so no DNS lookup is done and benchmark this setup. I think such a setup minimizes random network factors , so a latency is almost sure to be in the server and not *OUT THERE* :) Just my 2c.
On Sun, 2005-02-20 at 10:39 -0800, Grant wrote: > > The time needed to lookup is probably spend running a DNS lookup , I > > doubt changes to your apache can affect this in any way. There is always > > a latency associated with the network ( especially on a non-LAN ) , so > > don't try to get it faster that light :) For example , measure the ping > > round-trip time to the dns and to the server. You probably can't get any > > faster than the sum of the two times. > > What about the fact that the DNS lookup takes much longer if I haven't > clicked on anything for a little bit? Is that because of some type of > DNS caching in the browser? Could this have anything to do with my > site's DNS server's performance? > > - Grant > > -- > [email protected] mailing list > > -- Ivan Yosifov. -- [email protected] mailing list
