Re:Show HN: AWS CloudFront (CDN) for dynamically generated c...
by zubairov on Thursday May 10, 2012 @07:04AM
(#3952810)
Hi,
No 1005 ms was not a cache miss it was a request to the origin server. Latency was 799 ms.
I assume CloudFront will contribute some latency, however in our case (we are using Heroku) our servers were already on Amazon platform, therefore CloudFront --> our server latency should be significantly lower. So CloudFront cache miss latency for the enduser will be not significantly higher than origin server latency for the enduser.
Re:Show HN: AWS CloudFront (CDN) for dynamically generated c...
by madarco on Thursday May 10, 2012 @08:01AM
(#3952992)
Thanks,
I've asked because I've read somewhere that an average request for a "Miss from cloudfront" object was ~1 second, and I thought that your data was confirming that value.
No 1005 ms was not a cache miss it was a request to the origin server. Latency was 799 ms.
I assume CloudFront will contribute some latency, however in our case (we are using Heroku) our servers were already on Amazon platform, therefore CloudFront --> our server latency should be significantly lower. So CloudFront cache miss latency for the enduser will be not significantly higher than origin server latency for the enduser.