Emilio
Emilio
CDCloudflare Developers
Created by Lukas on 12/17/2024 in #workers-help
Hyperdrive database host string too short?
Hi @Lukas thanks for bringing this up. This was an issue with field validation in the UI and we've implemented a fix, which should be released by tomorrow. In the meantime you can create your Hyperdrive config via the Wrangler CLI, through our API or with Terraform.
7 replies
CDCloudflare Developers
Created by elithrar on 11/7/2023 in #queues
No: batch timeout is on the producer
That sounds like a tricky architectural issue. It's possible that Queues is not the right tool for this use case if you have long running tasks given our cap on simultaneous outbound connections. Have you considered using Durable Objects without Queues? Or you might also be able to use a relational database to keep track of your "jobs" and their statuses, it's possible that D1 could do the trick. From there you could have a cron trigger to wake up and dispatch a worker to work on each incomplete job.
6 replies
CDCloudflare Developers
Created by elithrar on 11/7/2023 in #queues
No: batch timeout is on the producer
Consumer concurrency works via an additive increase, multiplicative decrease. But we only start increasing the concurrency when a consumer successfully processes a batch of messages. So by limiting your batch sizes to 1, our queue broker can't scale you up quickly wrt to the size of your backlog.
6 replies
CDCloudflare Developers
Created by elithrar on 11/7/2023 in #queues
No: batch timeout is on the producer
Hey Nil, I took a look at your Queue and Consumer and it looks like you're using a "batch_size" of 1. This means the producer only sends one message at a time to the consumer. We generally discourage this. I'd recommend increasing the batch size, and you should see much better processing time.
6 replies
CDCloudflare Developers
Created by Elliot Hesp on 5/30/2023 in #queues
Specifying Queues per environment in wra...
Yeah, looks like a toml syntax issue. For others reading this thread, fully specifying [[env.production.queues.producers]] is the solution.
2 replies