1 The following is a demonstration of the weblatency.d script.
3 Here we run weblatency.d while a mozilla browser loads the
4 http://www.planetsolaris.org website. After the website was loaded, Ctrl-C
5 was hit to print the following report,
8 Tracing... Hit Ctrl-C to end.
12 images.pegasosppc.com 1
13 www.planetsolaris.org 5
19 images.pegasosppc.com 491
20 www.planetsolaris.org 757
24 images.pegasosppc.com 491
26 www.planetsolaris.org 3689
28 This gives us an understanding on which hosts were responsible for the
29 time endured while loading the website. It turns out that requests to
30 www.planetsolaris.org were the slowest, with a maximum time of 3.7 seconds
31 (probably the first request, which incurred a DNS lookup).
35 The following shows the same google lookup performed on a number of sites,
38 Tracing... Hit Ctrl-C to end.
58 From the average time you would guess that I was running this from
59 New Zealand (the fastest), with times to the other hosts following suit
60 (Australia, USA, UK). I was actually running this from Australia - it's
61 interesting that the New Zealand server responded slightly faster.
66 Now several websites are loaded as a larger demonstration,
69 Tracing... Hit Ctrl-C to end.
73 static.technorati.com 1
74 sunopensolaris.112.2o7.net 1
77 sunglobal.112.2o7.net 2
78 embed.technorati.com 2
80 fdimages.fairfax.com.au 4
82 bugs.opensolaris.org 7
88 sunglobal.112.2o7.net 0
93 fdimages.fairfax.com.au 88
95 bugs.opensolaris.org 162
96 static.technorati.com 350
98 embed.technorati.com 632
99 sunopensolaris.112.2o7.net 900
103 sunglobal.112.2o7.net 0
106 fdimages.fairfax.com.au 243
110 static.technorati.com 350
112 bugs.opensolaris.org 560
113 sunopensolaris.112.2o7.net 900
114 embed.technorati.com 973
116 It's interesting that the most common host (www.smh.com.au, NUM == 51),
117 responded with a fast AVGTIME (73 ms). The reason for this may be due to
118 cacheing by my proxy server. Less common hosts such as embed.technorati.com
123 The results from weblatency.d are interesting, but they don't point the
124 finger at one single cause for website latency. The value here is the response
125 time experienced by the client - which is a combination of many response
126 times (link speeds, proxy server, DNS server, web server).