What is the average response time in the case of a cache hit and in the case of a miss?
These numbers vary depending from site to site depending on the sites’ users’ access patterns and the sites’ connection speeds to the Internet. As one example, Cobalt Networks, Inc. (located in Mountain View, California) currently connects to the Internet via a T1 to above.net, our ISP. On our internal CacheQube we see average hit times of typically one to two hundred milliseconds. This includes the time to send the complete hit object’s contents out onto the local network to the client. We see average miss times of typically between one and two seconds. Miss times would be higher if Cobalt was connected to the Internet at a lower speed or if more of our requested content were from overseas. As it is, much of our users’ request content is served relatively locally, i.e., from servers in North America.
