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: Patrick Radtke <>
  • To: Nick Roy <>
  • Cc: Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] Latency figures for CDNs
  • Date: Fri, 26 Aug 2016 08:20:24 -0700
  • Ironport-phdr: 9a23:4EFvuBV36JP3pdQSJcwxmDDFV0/V8LGtZVwlr6E/grcLSJyIuqrYZhSGt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3HUNPK+/0Ao/fidisn6D3osWLIlYAuD3oR7J5L12MqhSZ4s8MhppKK6AtxwHPr2cSPela2DU7C0iUmkPE79uq/ZVgux5Zt+4i+oYUSazmZaUzTpRTDS48Lns06MDtqRjfXE2E4X5KATZeqQZBHwWQtEKyZZz2qCav87MlgCQ=

I think it is unfortunate that they did not compare with a non-CDN
solution, or show the 'backbone' testing so we could see what portion
of the time was on the last mile vs accessing the CDN vs accessing a
non-CDN.

As for distribute large aggregates: any issues I've encountered with
large aggregates are related to memory consumption and signature
verification time on my end, and client processing time is much
greater than download time. I don't think I'd notice changes in
download time for the large aggregate, in particular because it
happens in the background.

-Patrick



Archive powered by MHonArc 2.6.19.

Top of Page