High latency on certain endpoints, can't get Smart Placement working so far
Hey, I'm experiencing pretty high latencies on certain endpoints on a Worker I'm working on, very probably because the Planetscale DB is in Europe and I'm in Perú (although my cofounder being in Frankfurt/Germany also experiences almost 2s slow endpoints which should be pretty close to the db and therefore faster right?), so I'm experimenting with Smart Placement, but as I'm in Perú I can't manually drive European requests and this Worker is still in dev so there's almost no requests other than mine and occasionally my co-founders so I thought trying https://geofetcher.appsinprogress.com/ to generate traffic from Germany, though when logging the
cf-ipcountry header from my Worker I always get Perú, which is confusing , so I spun up my own fly.io machine in Europe which was supposed to periodically fetch my Worker but I still get USA, trying https://worldpagespeed.fly.dev/ I get Chicago for all their regions 😵💫 any tip on how to "make" smart placement interested in a European location to understand if that reduces the latency? 😇 Also note that from that european fly machine the latency is only about 1/3 around 60ms so it seems very likely to be location related. I'm trying the D1 workaround but so far it doesn't seem to work, as also mentioned there it's not guaranteed 😔 would really love an option to manually specify a location for a Worker1 Reply
Interestingly I now get
"placement_status": "SUCCESS" which is great, and the mentioned endpoints are much faster now, though it's still "cf-placement":null 🤔
Also might be due to the D1 with location hint I bound to my Worker, although I'm not (yet) actually using it 🤷♂️