Workers cache is missing most of the time

I set up a worker who is running a couple of fetches referencing this example. I setup s-maxage to 600 so I was expecting it to serve the cache response over 90% times but when I checked the analytics dashboard, I realized it’s around %30 in every region. What am I doing wrong? Is this expected?

Example endpoint: https://apptslots.carbonhealth.com/?locationId=05af5710-bd5e-467d-bd7d-8f5f9f0a8e99&specialtyId=0ad3697e-1ce1-4118-b355-d1b3dd9540ee&timezone=America%2FLos_Angeles

Screenshots: Imgur: The magic of the Internet

As it looks like a ten minute TTL (which sounds logical for your content), that will contribute to more frequent MISSes. Especially considering that it takes a few requests through that datacenter to start getting a HIT at that datacenter. Repeat this for every URL and every data center that receives traffic and I can see how you’d end up at 30%.

The only thing left to try is enabling Argo Tiered Caching. Granted, it looks like your data is pretty regional, but tiered caching might help a bit.

1 Like

I will check this. Thanks @sdayman !

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.