Wampum

I'm back to using my VSAT, so I haven't bothered to download the chrome binary (that's what visits to wifi hot spots are for, along with the designer coffee), but others have and there is a significant difference (as in "very bad") between the Google Corporation's chrome and the Mozilla Foundation's firefox browsers.

Two machines with flushed caches loaded the default page for www.berkeley.edu. The chrome machine immediately queried for the hostnames for *all* of the links on that page, even though that browser had not yet visited any of them.

Another test was run once with Firefox (with all the various extensions turned off) and then again with Chrome (after flushing the windows DNS cache). The sample of websites is CNN, BBC, Washington Post, a few web comics, a weather site, slashdot, the register.

Firefox generated 194 DNS packets (queries and responses)
Chrome generated 638 DNS packets (queries and responses)
Chrome was 3.289x the query load of Firefox.

Because both use the publicsuffix.org, see ttps://wiki.mozilla.org/Gecko:Effective_TLD_List, a really silly idea in so many ways, the .co registry is going to get really hammered. I've no idea if Google is picking up the load at the Universidad de Los Andes, which runs the NIC for Columbia.