Smart Placement
I have three Workers apps (2 SSR/fullstack; 1 SPA) which connect to a Worker "service" that makes the API requests to the external services they need. The service is a WorkerEntrypoint and the app Workers connect to it via Service Bindings and make RPC calls to it and it calls the API endpoints.
The users are mostly in South/East Africa but the origin servers are in Germany/Ireland. The reason I did the architecture this way was thinking that by enabling Smart Placement on the service it'd be moved close to the origins while the apps ran on the Workers near the users in Africa (or the US while we're developing it).
However, the dashboard says "Your Worker has not received enough requests to make a placement decision". Production (with no real users) has gotten 455k requests in the last month. Dev (with US traffic from us developers) has 680k+ in the last moth. What's "enough"?
Is there anything I can do to debug this further or encourage/ensure the service worker is running close to the origin servers it's talking to?
The users are mostly in South/East Africa but the origin servers are in Germany/Ireland. The reason I did the architecture this way was thinking that by enabling Smart Placement on the service it'd be moved close to the origins while the apps ran on the Workers near the users in Africa (or the US while we're developing it).
However, the dashboard says "Your Worker has not received enough requests to make a placement decision". Production (with no real users) has gotten 455k requests in the last month. Dev (with US traffic from us developers) has 680k+ in the last moth. What's "enough"?
Is there anything I can do to debug this further or encourage/ensure the service worker is running close to the origin servers it's talking to?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
