That behavior is probably fine for you, since if you're checking on every request a user is likely to hit the same DC every request and so will hit the cache.
It's just showing in which datacenter the Durable Object will end up in, if the user hits the one you've selected. colo = colocation, renting space in an existing DC, which roughly equals datacenter yea. The dotted lines go to the place where the DO would be created.
I'd recommend you wait until you actually see the amount of traffic you're getting to optimize further. At a certain point the amount of effort it takes to optimize things is a lot of work, work that might not even be needed if you see that the caching from BetterKV or otherwise is working well enough.
Makes sense. Do cloudflare's analytic tools let me see traffic from specific KV namespaces? I have a "codes" table for email codes and "session" table for sessions. Also, can I analyze other things like D1 traffic and worker CPU times?
I was looking at pricing, and is the pricing on the default page here: https://www.cloudflare.com/plans/ for pages? The prices are the same but there's two different sections which is confusing.
As far as I know you can't get KV analytics per namespace except size, no request stats. D1 has really nice GraphQL Analytics and you can get all sorts of analytics per DB and even per query analytics Worker CPU Time is through GraphQL as well