Current time: 01-23-2020, 06:17 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Crazy First Byte Times
01-12-2012, 05:01 PM (This post was last modified: 01-13-2012 05:44 AM by pmeenan.)
Post: #4
RE: Crazy First Byte Times
OK, I'll have to change the direction I was heading, because (as I've just learned) CloudFront doesn't honor the Cache-Control headers. Sorry about that.

However, (using http://www.webpagetest.org/result/110601...#request45 as an example) since that object wasn't already in the CloudFront cache, the time to get that object from the origin is included in the Time to First Byte metric.

I agree that the times seem unusually long, but that's sometimes why people use a service such as CloudFront-- to shield their users from latency problems at their origin.

Retrieving that object directly from your origin takes me on the order of 2.7 seconds from New York, and about 3.3 seconds from San Francisco. (I tried it only twice from each location.) (And of course those times are going to show up directly in your Time to First Byte metric.)

I have tested this object, and it seems to continually show up as a "X-Cache: Miss from cloudfront", so we are looking deeper to see if we can tell why it's not staying in cache.

Does this help, or am I misunderstanding what you're trying to resolve?
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Crazy First Byte Times - slowinaz - 10-15-2011, 09:33 PM
RE: Crazy First Byte Times - pmeenan - 10-17-2011, 10:56 PM
RE: Crazy First Byte Times - copysa1211 - 01-12-2012, 04:57 PM
RE: Crazy First Byte Times - copysa1211 - 01-12-2012 05:01 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)