You can optionally use ping latency to figure out how things are getting on but it is not very accurate and it is only a very broad parameter and not a very good method. But I am sure that does serve as a smoking gun to prove that things are wrong and you can use it for further testing and analysis.
The ping times should be within 400 ms for most paths. On Sun, Jan 5, 2014 at 4:37 PM, Girish Venkatachalam <[email protected]> wrote: > On Sun, Jan 5, 2014 at 12:01 PM, Vinoth Marimuthu > <[email protected]> wrote: >> Hi, >> >> I was using OpenDNS but it was very slow and I tried Google DNS last week; >> the connection speed is very good. My knowledge one networking is >> limited. Could you please help me to understand the difference between >> OpenDNS and GoogleDNS and which one is best? >> > > We all start with limited knowledge. That is perfectly normal. > > DNS queries cannot limit the network speed and cannot be the > bottleneck unless you have a really broken > DNS server. > > You can measure the time taken with the command > > $ time dig www.mit.edu > > or something to make sure it does not come from the cache. > > Usually network slowness is caused due to either a wireless link or a > badly provisioned copper link or > some similar issue at the exchange/ISP end. > > There may also be slowness due to other computers on the local LAN > that are downloading big files. > > Netflow is a tool used in the network periphery device like router or > MODEM to figure out how your network > is being used. > > But netflow can only tell you about local problems. > > www.speedtest.net > > can tell you about your ISP and its latency. > > -Girish > > -- > Gayatri Hitech > http://gayatri-hitech.com -- Gayatri Hitech http://gayatri-hitech.com _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc ILUGC Mailing List Guidelines: http://ilugc.in/mailinglist-guidelines
