We're testing out latencies before we
We're testing out latencies before we can go all-in on cloudflare workers. Considering a single request may have multiple hops between db and worker the latencies are not acceptable when distributing globally. We've kept smart placement on to try and force it to keep it closer to the db but it's been days and multiple requests and we're still seeing local placement. Given that we can't reliably place and predict our workers, it's hard to justify this lock-in. Would the team be able to share how we can reliably hint / enforce smart placement to kick in?
2 Replies
What latencies are you looking for? Numbers would help, perhaps this is something we can assist with
Concluded this in DMs. Will chat with you on it.