Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] Latency figures for CDNs

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] Latency figures for CDNs


Chronological Thread 
  • From: Tom Scavo <>
  • To: Patrick Radtke <>
  • Cc: Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] Latency figures for CDNs
  • Date: Tue, 6 Sep 2016 11:15:45 -0400
  • Ironport-phdr: 9a23:pkFfZxy0ctlR4kDXCy+O+j09IxM/srCxBDY+r6Qd0eoXIJqq85mqBkHD//Il1AaPBtqLra8fwLOL+4nbGkU+or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6aijSI4DUTAhTyMxZubqSwQ9aKzpf/6+fnw5TPeQRDh3KHaL9uLxj++R3YqtMXiohKIacr0AbSo3dFffhX2XIuLlWWyUXS/MC1qaJk9mxrsPs/8IYUTb/hdK0mSpRXCT0nNyY+48i95kqLdheG+nZJCjZeqRFPGQWQqUiiBpo=
On Thu, Sep 1, 2016 at 7:14 PM, Patrick Radtke
<>
wrote:
>
> I get, for a cache hit,
> 10-20 ms from an EC2 instance
> 33-50 ms from home
> cache misses seemed to add 1 second.
>
> If I hit the MDQ beta server directly I get
> 10-30 ms from EC2 instance (this surprised me)

This may be due to the fact that mdq-beta itself is an EC2 instance.

> 175-200 ms from home.

I'd be interested to know how much of that is DNS resolution, how much
is connection time, and how much is actually due to data preparation
(as opposed to data transfer).

Tom

Archive powered by MHonArc 2.6.19.

Top of Page