High latency in Worker-to-D1 queries despite low execution time in D1 metrics
🖥️D1✅Solved
Workers
WorkersI am experiencing a significant discrepancy between D1 execution time and the actual latency observed in Cloudflare Workers.
Setup: My D1 database is located in the Asia Pacific (APA) region.
The Issue: The D1 dashboard shows that each SQL query executes in under 1ms. However, my Worker logs indicate that even the simplest query (e.g., a basic SELECT) takes over 40ms to complete.
Troubleshooting: I suspect this is due to the physical distance between the Worker's edge location and the D1 storage node. To address this, I attempted to change the Smart Placement setting to "Smart".
Current Status: The dashboard consistently shows the message: "Your Worker has not received enough requests to make a placement decision." Question: Is there a way to manually force the Worker to be placed in the same region as the D1 database? Or what is the threshold of requests required for Smart Placement to take effect?
Setup: My D1 database is located in the Asia Pacific (APA) region.
The Issue: The D1 dashboard shows that each SQL query executes in under 1ms. However, my Worker logs indicate that even the simplest query (e.g., a basic SELECT) takes over 40ms to complete.
Troubleshooting: I suspect this is due to the physical distance between the Worker's edge location and the D1 storage node. To address this, I attempted to change the Smart Placement setting to "Smart".
Current Status: The dashboard consistently shows the message: "Your Worker has not received enough requests to make a placement decision." Question: Is there a way to manually force the Worker to be placed in the same region as the D1 database? Or what is the threshold of requests required for Smart Placement to take effect?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942Members
Resources
Similar Threads
Was this page helpful?
