Cache API within Workers does not support tiered caching. Tiered Cache concentrates connections to origin servers so they come from a small number of data centers rather than the full set of > network locations. Cache API is local to a data center, this means that cache.match does a lookup, cache.put stores a response, and cache.delete removes a stored response only in the cache of the data center that the Worker handling the request is in. Because these methods apply only to local cache, they will not work with tiered cache.
@RelexDanger #8 这我知道 所以我才好奇你咋预热 假设你服务器再HK 你咋预热HK之外的数据中心
@Maureen #11 cf自动同步的和操作无关
@RelexDanger #12 额 你是指这个定时调度是worker的？ worker还能主动发起请求吗
@RelexDanger #12 但我看你页面 总感觉是服务器到worker呀 不然怎么会只有9210次请求 我理解这是9210个图片吧
https://developers.cloudflare.com/workers/reference/how-the-cache-works/
看了下 你这应该就是预热的服务器命中的数据中心
开源了吗