text stringlengths 0 1.8k |
|---|
[1601.38 --> 1602.76] But that's, like, a separate conversation. |
[1603.42 --> 1608.42] However, we should absolutely try to serve as much as we can from the CDN. |
[1609.04 --> 1611.06] Especially when it comes to the static content. |
[1612.24 --> 1615.86] GIFs, PNGs, MP3s, all that stuff should be served directly from the CDN. |
[1615.86 --> 1618.60] Which is exactly what Adam was suggesting. |
[1619.32 --> 1619.62] Mm-hmm. |
[1620.46 --> 1624.12] I mean, it would be different if we had, like, an unreasonable ask for them. |
[1624.28 --> 1627.22] Like, if it was, like, terabytes and terabytes of data. |
[1627.42 --> 1628.24] Like, that's unreasonable. |
[1628.66 --> 1637.32] But if it's, like, sub 200 gigs, that's not unreasonable to ask a CDN to, in perpetuity, hold that until I'd say it's expired. |
[1637.90 --> 1638.78] What are you thinking, Jared? |
[1638.78 --> 1641.44] Well, this is what I've been saying for years. |
[1641.56 --> 1642.26] That's what I've been thinking. |
[1643.94 --> 1645.24] Well, I think this is, like, the... |
[1645.24 --> 1646.60] Okay, you're being facetious now, right? |
[1646.94 --> 1647.26] Facetious? |
[1647.28 --> 1648.60] No, facetious. |
[1648.74 --> 1649.24] No, I'm not. |
[1649.66 --> 1650.48] I've been saying for years. |
[1650.66 --> 1656.14] 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? |
[1656.14 --> 1664.74] And so I understand that, like, okay, if we're going to do what Adam proposes, you're kind of becoming a snowflake, right? |
[1664.82 --> 1666.58] Like, hey, Fastly, please treat us differently. |
[1667.00 --> 1675.70] But isn't there just, like, a way we can, that they can scale to all their customers to let them, to let you say, don't ever request this again, please? |
[1676.06 --> 1678.68] I would love to have that conversation with someone from Fastly. |
[1678.80 --> 1679.24] I've been trying for years. |
[1679.24 --> 1680.14] That's what I've been saying for years. |
[1680.14 --> 1682.42] I don't want them to keep asking me for new... |
[1682.42 --> 1685.52] My ship at 28.mp3 hasn't changed. |
[1685.62 --> 1686.38] It's not going to change. |
[1686.48 --> 1687.42] It's never going to change. |
[1687.84 --> 1688.84] We know it's never going to change. |
[1689.06 --> 1690.38] So, yeah. |
[1690.72 --> 1695.26] I will not name any names, the people that I reached out that I knew within Fastly. |
[1695.68 --> 1701.08] But if a listener knows someone within Fastly that wants to have this conversation, I would love to do that improvement. |
[1701.70 --> 1707.36] Because Honeycomb, this new integration, showed us how much can improve within the CDN. |
[1707.36 --> 1707.96] Yeah. |
[1707.96 --> 1716.04] And we are reaching diminishing returns within the app, within our own infrastructure, where the biggest wins right now are in the CDN. |
[1716.76 --> 1716.98] Right. |
[1717.70 --> 1723.08] For me, imposter syndrome sets in when I think, surely we're holding it wrong. |
[1723.16 --> 1728.58] You know, like the Steve Jobs response to the antenna on the iPhone 4 is you're holding it wrong. |
[1728.96 --> 1730.58] I feel like we're just not using Fastly right. |
[1730.58 --> 1732.58] Like, I think we're... |
[1732.58 --> 1734.60] I mean, I understand how to set HTTP headers. |
[1735.34 --> 1736.44] And we use ETags. |
[1736.70 --> 1737.92] And we set cache control. |
[1738.08 --> 1739.38] And we've tweaked some stuff. |
[1739.38 --> 1743.20] But I just feel like we're not using it right for some reason. |
[1743.30 --> 1746.34] And that's why part of me is just wondering. |
[1746.92 --> 1748.44] That's where I like the toiling away is. |
[1748.52 --> 1751.86] Like, well, how many times can we tweak the way that we tell Fastly to do things? |
[1752.40 --> 1752.68] Mm-hmm. |
[1752.68 --> 1755.54] But I don't know. |
[1755.66 --> 1757.44] I just thought this is how CDNs work. |
[1757.52 --> 1759.38] It's like, hold on to it until it's fresh, please. |
[1760.10 --> 1763.30] That seems like a button you'd click in a click op somewhere. |
[1763.56 --> 1764.14] But I don't know. |
[1764.90 --> 1765.20] Yeah. |
[1765.20 --> 1771.26] So I do, like, I'm surprised when content that should be cached for... |
[1771.26 --> 1774.40] Now that I think of it, some of it is even cached, like, for a whole year. |
[1774.78 --> 1777.26] The stuff that we know is not going to change. |
[1778.00 --> 1784.60] And that content is being requested even though it was requested before. |
[1785.32 --> 1786.94] And it's requested again. |
[1787.08 --> 1788.14] And it hasn't passed a year. |
[1788.26 --> 1789.86] So what's going on Fastly? |
[1789.92 --> 1790.24] Right. |
[1790.58 --> 1790.98] Mm-hmm. |
[1791.36 --> 1792.52] I can't answer that. |
[1792.52 --> 1797.48] Our old episodes, the long tail of listens on our shows is bewilderingly awesome. |
[1797.66 --> 1801.46] Like, you go back to a show and you're like, wow, 33 people listen to this today. |
[1801.64 --> 1803.32] And it's four years old. |
[1803.80 --> 1805.90] Like, every day our MP3s are being requested. |
[1806.38 --> 1807.26] Pretty much all of them. |
[1807.64 --> 1809.94] You know, plus or minus some outliers. |
[1810.26 --> 1817.10] So they shouldn't be expiring unless you set the expiration to an hour or 30 minutes or six hours. |
[1817.10 --> 1822.44] But if we're setting it to a long time, I just, I do not understand why we have so many cash misses. |
[1823.34 --> 1830.42] Especially, I mean, given, it'd be different if we, if our content was highly volatile in terms of change. |
[1830.86 --> 1831.90] We're a media company. |
[1832.08 --> 1833.92] The things we create are long-term artifacts. |
[1834.32 --> 1839.64] So just by nature of the business we're bringing, like the character type we are, the persona, so to speak, even. |
[1839.98 --> 1840.20] Yeah. |
[1840.58 --> 1844.66] You know, we know that the reason we're using the CDN is to be globally fast. |
[1844.98 --> 1845.38] Right. |
[1845.38 --> 1850.38] And the data we're giving them to be globally fast doesn't change if ever. |
[1850.86 --> 1851.16] Mm-hmm. |
[1851.38 --> 1856.36] So we want to be globally fast forever and pay for that. |
[1856.78 --> 1857.18] Right. |
[1857.58 --> 1864.42] And we put fast in front of everything to enable that so that even if our app is down, we're still serving cash pages. |
[1864.84 --> 1869.32] And the same thing for our actual files, like MP3s and GIFs and things like that. |
[1869.38 --> 1877.12] Like just by the nature of us being a media company or a media entity, the things we tend to, the things we have tend to never change. |
[1877.32 --> 1877.48] Like it. |
[1877.98 --> 1878.20] Yeah. |
[1878.20 --> 1883.80] I think we've changed like an episode just to go back and update what we called a remastering where we're doing that for a bit. |
[1883.88 --> 1889.68] We're remastering some of these shows Jerry's talking about that had high degrees of listens that are several years old. |
[1890.18 --> 1898.82] So rather than like having that listener go back and listen to an old show and still be sort of like unimpressed by the audio quality in comparison to now, we went back and remastered those. |
[1899.88 --> 1906.26] But we can also programmatically purge endpoints from Fastly by way of our system. |
[1906.26 --> 1906.84] So you could. |
[1907.04 --> 1907.18] Right. |
[1907.50 --> 1908.94] It'd be easy to code that up. |
[1909.50 --> 1910.08] I just don't. |
[1910.22 --> 1913.52] I've never done it because I feel like it keeps purging anyways. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.