Kris
CDCloudflare Developers
•Created by Kris on 1/3/2025 in #workers-help
pnpm with Workers Builds
Thanks, yes, I've set
PNPM_VERSION so an update doesn't break the build. I just wish it got the value from .tool-versions so I don't need to remember to update the build config when we change the version.9 replies
CDCloudflare Developers
•Created by Kris on 1/3/2025 in #workers-help
pnpm with Workers Builds
It seems I need to make
.tools-versions match the installed versions, or override the installed versions to match .tools-versions. Too bad Workers Builds doesn't just pick up the versions in .tools-versions when setting up the environment.9 replies
CDCloudflare Developers
•Created by Kodie Goodwin on 10/23/2023 in #workers-help
Queues CPU Limits
Can confirm it's 15 minutes for queue consumers.
3 replies
CDCloudflare Developers
•Created by Kris on 7/11/2023 in #workers-help
Long-running worker performance
Running the worker locally against the production DB leads to durations about 50% as long as production workers. Seems to suggest the primary issue is DB performance. I'll dig into DB query optimization first. I'm also going to try deploying the sync task as a Supabase edge function instead of a Cloudflare worker to see if that performs better.
7 replies
CDCloudflare Developers
•Created by Kris on 7/11/2023 in #workers-help
Long-running worker performance
Yeah, I've enabled Smart Placement, but it had no noticeable effect on execution duration.
7 replies
CDCloudflare Developers
•Created by Kris on 7/11/2023 in #workers-help
Long-running worker performance
Some 99th percentile stats:
- CPU time: 3,053.7 ms
- Execution duration: 41.5 GB-sec
- Subrequests: ~10 per request (at least, according to the metrics reported)
7 replies