Smart Placement choosing potentially suboptimal locations
Our application https://mattrax-bdc.pages.dev connects to a DB hosted in the US, and we're developing from Perth, Australia.
We've got Smart Placement enabled, but I'm not sure that the best location is being chosen to run our functions.
Response headers indicate that the function is being executed in Singapore, rather in the US closer to our DB. For context, we use
fetch to query our db since tcp connect doesn't seem to affect Smart Placement.
I'd expect that since our function makes multiple round trips to our DB, it would choose a US placement, hopefully adding to the already 400ms (33%) reduction in latency that Smart Placement is providing.
Account ID: f02b3ef168fe64129e9941b4fb2e4dc10 Replies