text stringlengths 0 1.8k |
|---|
[1914.56 --> 1918.86] You know, and every once in a while I'll hop in there and just purge one manually, especially if it just released. |
[1919.04 --> 1919.90] I feel like we're holding it wrong. |
[1920.14 --> 1920.58] I do. |
[1920.66 --> 1923.44] I feel like I don't know why we're holding it wrong. |
[1923.56 --> 1928.32] It seems like the logical way a CDN should work is the way we think it does work. |
[1929.04 --> 1931.64] Yet we are holding it seemingly wrong. |
[1931.64 --> 1938.26] So, yeah, I say listeners, if you're out there, if you know somebody in Fastly who knows more than we do, we have connections there. |
[1938.32 --> 1941.40] But, you know, we've hit certain dead ends on that front. |
[1941.74 --> 1943.44] But, yeah, we'd love to have some help. |
[1943.62 --> 1945.36] Like Fastly, come on this show. |
[1945.54 --> 1954.50] Come on YouTube with Gerhard and Triage how we use our CDN and help us, you know, de-antenigate ourselves and hold it right. |
[1955.02 --> 1955.48] You know what I mean? |
[1955.48 --> 1956.38] Like, yes. |
[1956.50 --> 1957.88] Let's not CDN gate ourselves. |
[1958.02 --> 1961.36] Over the years, we had some epic support threads with Fastly. |
[1961.88 --> 1962.32] Like, epic. |
[1963.24 --> 1965.00] Some of them have not been solved. |
[1966.52 --> 1967.28] Unsolved mysteries. |
[1968.32 --> 1970.56] Many unsolved mysteries when it comes to Fastly. |
[1970.80 --> 1972.30] Let's hold it right, please. |
[1972.46 --> 1972.98] I'm looking. |
[1973.18 --> 1975.18] So, I think we're holding it right. |
[1975.50 --> 1978.78] But I think there's stuff happening within Fastly which we don't fully understand. |
[1978.90 --> 1979.12] Right. |
[1979.78 --> 1981.44] And maybe that's just how it works. |
[1982.10 --> 1984.10] It doesn't make sense why it is that way. |
[1984.10 --> 1990.92] So, if it works that way and that's how it does work, that seems odd given the reason you use a CDN. |
[1992.24 --> 1992.94] I mean. |
[1993.14 --> 1994.62] I think we can Kaizen Fastly. |
[1995.10 --> 1997.58] I think that's what you're getting to. |
[1997.78 --> 1997.98] Yeah. |
[1998.12 --> 1998.28] Yeah. |
[1998.38 --> 2007.06] Because in the last 24 hours, we had 3,000 misses on MP3 files. |
[2009.16 --> 2010.96] This is in the last 24 hours. |
[2011.20 --> 2012.42] Oh, that's terrible. |
[2012.42 --> 2013.92] Doesn't make sense. |
[2013.92 --> 2014.12] Doesn't make sense. |
[2014.28 --> 2014.64] Exactly. |
[2015.16 --> 2015.86] Doesn't make sense. |
[2016.68 --> 2027.18] The whole reason we engage with Fastly in the origin before we got to what we could do application-wise was to deliver our MP3s globally fast forever. |
[2027.56 --> 2028.04] Yep. |
[2028.04 --> 2043.42] So, to have 1,000 misses in the last 24 hours is bost |
[2043.42 --> 2044.92] too much data forever. |
[2045.42 --> 2045.72] Okay. |
[2045.88 --> 2046.14] Sure. |
[2046.20 --> 2046.94] We have to purge somewhere. |
[2047.36 --> 2047.60] Fine. |
[2047.60 --> 2049.86] Then have 1 pop be the canonical. |
[2049.86 --> 2050.92] That one is forever. |
[2051.32 --> 2055.46] And you can miss somewhere else and pull from your own pop fast, not from us. |
[2055.90 --> 2058.14] Well, we shield through LaGuardia, so we should have that. |
[2058.34 --> 2062.14] Like, LaGuardia should have it if Hong Kong doesn't. |
[2062.54 --> 2062.60] Exactly. |
[2062.60 --> 2066.98] So, I'm not super clear if that still shows up as a miss, if Hong Kong misses but grabs |
[2066.98 --> 2068.58] it from LaGuardia, doesn't grab it from us. |
[2068.84 --> 2069.76] Gary, you know the difference. |
[2071.82 --> 2072.22] Yeah. |
[2072.98 --> 2076.18] So, I'm not sure, but that's something worth digging into. |
[2076.36 --> 2077.88] So, this is exactly like… |
[2077.88 --> 2078.58] Let's solve this mystery. |
[2079.00 --> 2079.34] Exactly. |
[2079.44 --> 2081.08] How does this stuff work within Fastly? |
[2081.16 --> 2086.18] Like, this is the first time we could have a really good conversation about this because |
[2086.18 --> 2086.92] of this integration. |
[2087.12 --> 2087.84] We have data. |
[2088.20 --> 2089.12] We have wisdom. |
[2089.58 --> 2089.74] Yeah. |
[2090.18 --> 2091.18] Before we had assumption. |
[2091.44 --> 2094.02] Now we have, like, look, here's Honeycomb. |
[2094.20 --> 2094.62] Hard facts. |
[2094.62 --> 2095.74] This is where it goes. |
[2095.86 --> 2096.68] This is how it works. |
[2097.02 --> 2097.24] Yeah. |
[2097.88 --> 2098.08] Yeah. |
[2098.18 --> 2098.90] It's amazing. |
[2098.90 --> 2103.82] You know, even asking for support makes it so much harder when you have no visibility |
[2103.82 --> 2105.58] into what's going on. |
[2105.64 --> 2106.24] Now we do. |
[2106.62 --> 2112.42] So, we are armed with more data to support ourselves differently in our argument back |
[2112.42 --> 2115.52] like why things are not working the way they should be or how we think it should be. |
[2115.96 --> 2116.16] Yeah. |
[2116.16 --> 2116.24] Yeah. |
[2128.90 --> 2136.02] This episode is brought to you by our friends at Incident.io. |
[2136.40 --> 2140.68] Every software team on the planet has to manage incidents and a very large percentage of those |
[2140.68 --> 2142.62] teams are using Slack to communicate. |
[2142.84 --> 2143.76] That includes us. |
[2144.10 --> 2149.02] With Incident.io, you can create, manage, and resolve incidents directly inside Slack. |
[2149.28 --> 2150.24] Here's how it works. |
[2150.24 --> 2152.56] Head to Incident.io and sign up for free. |
[2152.76 --> 2154.20] Then add it to your Slack. |
[2154.20 --> 2158.24] From there, you have a brand new Incidents channel where all incidents get announced. |
[2158.62 --> 2161.28] Use the slash incident command to create and manage incidents. |
[2161.60 --> 2166.54] This command lets you share updates, assign roles, set important links, and more, all |
[2166.54 --> 2168.16] without ever leaving the Incident channel. |
[2168.58 --> 2174.10] Each Incident gets their own Slack channel plus a high-res dashboard at Incident.io with |
[2174.10 --> 2176.04] the entire timeline from report to resolution. |
[2176.58 --> 2179.78] Get everyone on the same page from the moment they join the Incident and help stakeholders |
[2179.78 --> 2180.64] stay in the loop. |
[2181.00 --> 2184.12] Add Incident.io to your Slack today and prove to yourself and your team. |
[2184.12 --> 2186.74] that they have everything you need to streamline your incident management. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.