On 21/05/2010 5:21 p.m., Alastair Johnson wrote:
I wish that were the case; but many web2.0/social
sites these days do have massive numbers of DNS transactions due to
the number of advertising networks, CDNs, and various embedded
contents. Often it's with a fairly low TTL or dynamically generated
fqdns (as Joe pointed out).
A major gripe I have with Google Analytics is, depending on the browsers
rendering priorities, can cause a page to _load_ slowly even though the
user has received 100% of the content.
All these third party analytics solutions are causing a lot of
additional rendering delays than many would think, and it's partially
the additional DNS lookup, as well as then requesting from a remote server.
I think it's the trend of the new bread of websites (I hate the term
web2.0, as I would call it web0.2a), and it's something that needs to be
addressed be it at the production end AND the delivery end.
Things change, for better, or for worse, and we need to keep up with
demand. Glue and tape anyone ?