The master feed, which is by the way, the one who takes the longest, I think that's a good one. So we upgraded Postgres and we got a little bit faster in our cache miss responses on our feed endpoints. But again, like we would need to continue digging to see like, what client where which data sent it's coming from things like that. Maybe it's location specific, right? It's a client, for example, from Asia, which is going to Ashburn. That's going to be the most important part of the wrong place.

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode