Web Content and South Pacific Latency Research
This post will be dedicated for researching the effect of latency on media (images) download time and user experience of content delivered across the Pacific Ocean
This ongoing research will try to find optimized delivery methods for AU/NZ companies trying to utilize the web for European and US based customers.
I will be using a 800X600 jpeg image of 207,506 bytes and examine its delivery time from the following 5 locations:
Yahoo’s glabal distribution Network (Flickr)
Google’s global distribution Network (Picasa)
The photo has been taken during a contract I had with Palo Alto’s Metacafe Inc. in Tel-Aviv last year and is showing the port of old Jaffa (upper left) from the 30th floor of the Metacafe tower (a.k.a Migdal Shalom).
I will be posting weekly updates on this pages that will summarize response and download time of these resources(images) from different locations around the world.
Those collected statistics will later be used for pointing out methods for optimizing rich content web delivery across the globe by south pacific based companies.
The research will focus on scenarios where the actual dynamic content (XHTML component of the page) is required to be served out of AU/NZ due to the publishing business’s requirements (a common case where some of the content is frequently updated against internal business data).
The research has been done using Pingdom Tools and other data centers across the world for collecting statistics of a pages and media delivered from New Zealand, USA and Europe.
Another resource is the Location Tracker (based on the great GeoIP database) that may assist by deciding where the media files should be resourced from (according to the customers actual physical location).
Tags: Latency NZ AU web
July 29th, 2008 at 3:29 am
[…] below latitude 32 south « Image Text Recognition and Google Maps StreetView Technology Web Content and South Pacific Latency Research […]
August 11th, 2008 at 1:05 am
caching is the key! let Proxies d the job for you:
October 31st, 2008 at 6:20 pm
check out some cool latency tools at : http://pagetest.getrpo.com/
December 18th, 2008 at 5:33 am
Nice pic!
September 4th, 2009 at 7:39 pm
[…] I have got into BGP4 from my work on GeoWeb apps a few years ago when I realised that with BGP4 and dynamically created routing tables you cannot rely on IP address alone for identifying a requesting connection’s physical location (see here). […]