From c78cd14770defae4b8bca9580b6ecf160333821a Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Thu, 9 Jan 2025 14:41:42 +0000 Subject: [PATCH] Adds info about Load Balancing interaction --- src/content/docs/cache/how-to/tiered-cache.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/cache/how-to/tiered-cache.mdx b/src/content/docs/cache/how-to/tiered-cache.mdx index 7d4b2a9099931cb..f85141e6e4062c9 100644 --- a/src/content/docs/cache/how-to/tiered-cache.mdx +++ b/src/content/docs/cache/how-to/tiered-cache.mdx @@ -22,6 +22,10 @@ Cloudflare allows you to select your cache topology so that you have control ove Smart Tiered Cache dynamically selects the single closest upper tier for each of your website’s origins with no configuration required, using our in-house performance and routing data. Cloudflare collects latency data for each request to an origin, and uses the latency data to determine how well any upper-tier data center is connected with an origin. As a result, Cloudflare can select the data center with the lowest latency to be the upper-tier for an origin. +#### Load Balancing interaction + +While Smart Tiered Cache selects one Upper Tier per origin, when using Load Balancing, Smart Tiered Cache will select the single best Upper Tier for the entire Load Balancing Pool. + #### Caveats Smart Tiered Cache does not work when an origin is behind an [anycast](https://www.cloudflare.com/en-gb/learning/cdn/glossary/anycast-network/) or a regional unicast network because that will prevent us from knowing where the origin is located. As a result, we are unable to select the optimal upper tier and latency may be negatively impacted.