text
stringlengths
0
1.8k
**Gerhard Lazu:** Let's see... How big is it? We have that as well, that information. Body size... 18 kilobytes? No, it can't be.
**Jerod Santo:** No. Megabytes.
**Gerhard Lazu:** Like 18 million... Let's see.
**Adam Stacoviak:** Should we ask Siri to do some math for us again?
**Gerhard Lazu:** Yes, Siri. 18 million bytes.
**Jerod Santo:** We should ask Honeycomb to do that math for us.
**Gerhard Lazu:** Right. So that's the one thing which we need to set. I was setting some derived queries... But let's see. But not for this specific thing. 17 kilobytes -- 17 megabytes.
**Adam Stacoviak:** Yeah.
**Gerhard Lazu:** We have a 17-megabyte GIF. And serving it to Hong Kong, that’s how long it takes.
**Adam Stacoviak:** It’s pretty heavy, yeah.
**Jerod Santo:** Yeah Sometimes we do lazy-load those, so you're not actually waiting end user experience. You can read what the news item is, and then as long as it takes a minute and a half to read, by then the image is loaded; it's still too long, but...
**Adam Stacoviak:** Yeah. Well, I don't think anybody's optimizing for reading -- unless your image, or something like that. Maybe you're optimizing for those things to be super-fast; large GIFs like that, for example.
**Jerod Santo:** Well, if we had it on a CDN in Hong Kong, it would be much faster.
**Adam Stacoviak:** Okay. That's the question I was thinking of asking... Like, okay, the observability lets us know this event happened, right? The event being this GIF was served from New York to Hong Kong at this speed, it's this size, etc.
The other question is it was a miss - so why was it a miss? These are questions we'll begin to answer ourselves as we dig into this. Okay, why was it a miss? Okay, now we know, and we’ve figured... What was the answer to that? Why was it a miss? Why was it a cache miss?
**Jerod Santo:** First, Hong Kong visitor of the day... Or it's expired, or who knows...
**Gerhard Lazu:** Yeah. I mean, those are kept in cache right on Fastly, and they can't cache like the entire Internet. Even for us, they can’t the cache all of our content.
**Jerod Santo:** They can probably cache all of our content at all of their pops, and barely ever notice, don't you think?
**Gerhard Lazu:** They could, but I think the reason why they're not is because they have to shed some of the extra content that is not accessed within, I don't know, x hours, days, whatever. So they don't guarantee that everything will be in the CDN all the time, even though our headers asked for it to be in CDN for a...
**Jerod Santo:** Right.
**Adam Stacoviak:** Why don't they just make people pay for that desire then? I guess if you're a larger site, with much more assets than we have, then maybe that becomes more and more expensive... But it's in our affordance right now to ask them to do that.
**Gerhard Lazu:** Yeah, that’s a great, great idea.
**Adam Stacoviak:** \[24:02\] So why wouldn't they offer it as a service, like "Hey, just cache the whole thing indefinitely, and I’ll pay for it."
**Gerhard Lazu:** I would love us to be able to do that. All our stuff should be cached all over the world. I agree.
**Adam Stacoviak:** What’s our assets on stuff like that? What would be the weight, in terabytes?
**Gerhard Lazu:** No...
**Jerod Santo:** No.
**Adam Stacoviak:** Or in Gigs?
**Gerhard Lazu:** 100-150 Gigs? Not that much.
**Adam Stacoviak:** That's pretty reasonable. I mean, I can go buy a 14-terabyte hard drive for under 400 bucks.
**Gerhard Lazu:** Yeah, but you need to multiply that times how many times you want, how many ops you want.
**Adam Stacoviak:** That’s true.
**Gerhard Lazu:** But still, you’re right, it's not a lot of data. I wish it was cached, and I wish we had an e-tag implementation, so that if the content doesn’t change, it won't expire from the cache. I mean, we have it configured, we have cache shielding, or pop shielding, which means that there should be at least o...
**Adam Stacoviak:** Right. And their network’s probably faster than ours.
**Gerhard Lazu:** Of course, yes.
**Adam Stacoviak:** Right. It should be at least, by design.
**Gerhard Lazu:** It's optimized, right? I mean, they should -- they have all the optimization, they have the best routing between their pops, which is how it should be. So you're right. But this, we've never had before, and this is the exciting thing. Now we know why our 99th percentile -- why we have such a bad tail ...
**Jerod Santo:** When does the law of diminishing returns come in?
**Adam Stacoviak:** The now known from the unknowns
**Gerhard Lazu:** I didn't hear any of you. \[laughs\] Do you want to try again?
**Jerod Santo:** When does the law of diminishing returns come in? Because you know, slow clients are slow. We can't make every request fast. Where do we know, "Now, we're just basically toiling away at something that's not worth our time anymore", versus "This is actually a valuable optimization"?
**Gerhard Lazu:** I'm really glad you brought this up, because we have -- this is something which we weren't able to see before... We have Apple Watches consuming MP3 files. And they are slow, so they take many, many minutes. Our longest consumer was something like 40 minutes. Imagine someone being connected to our web...
So when it comes to content that is not in the cache, I don't think we should spend much more time on that, except if we're talking about using an object store versus local store, but that's like a separate conversation. However, we should absolutely try to serve as much as we can from the CDN, especially when it comes...
**Adam Stacoviak:** I mean, it'd be different if we had an unreasonable ask from them; if it was like, terabytes and terabytes of data - that's unreasonable. But if it's like, sub-200 gigs, that's not unreasonable to ask a CDN, to in perpetuity hold that until it's expired.
**Gerhard Lazu:** What are you thinking, Jerod?
**Jerod Santo:** Well, this is what I've been saying for years. That's what I had been thinking. \[laughter\]
**Gerhard Lazu:** Okay, you're being facetious now, right? Facetious...
**Jerod Santo:** No. Facetious... No, I'm not. I've been saying it for years - can't they just cache our stuff forever, and just keep it and never request it again until we tell them that it's fresh? I understand that, okay, if we're going to do what Adam proposes, you're kind of becoming a snowflake, right? Like, "Hey...
**Gerhard Lazu:** I would love to have that conversation with someone from Fastly. I've been trying for years.
**Jerod Santo:** That’s what I’ve been saying for years. I don't want them to keep asking me for new --