I m on paid unbound plan so 600ms should

I'm on paid, unbound plan, so 600ms should not be my CPU limit.

kikaOP•3/17/23, 2:29 PM

kikaOP•3/17/23, 2:32 PM

DM'd the account ID

Matt Silverlock•3/17/23, 6:14 PM

@kikap_ - what error are you actually seeing though? Unbound doesn't mean 15 minutes of CPU time here.

kikaOP•3/17/23, 7:05 PM

@Matt you mean seeing in the logs? because since it's a "headless" worker, I don't see anything, except for the fact that I expect much more than 1000 items in the KV.

kikaOP•3/17/23, 7:05 PM

question though: each write to the queue counts as a subrequest too?

Matt Silverlock•3/17/23, 7:06 PM

Each time you call .send().send() - yes

Matt Silverlock•3/17/23, 7:06 PM

.sendBatch().sendBatch() is only 1 - and if you can do some batching on the client/producer side, you should

kikaOP•3/17/23, 7:07 PM

okay, so that's probably my problem. I just exchanged KV ops/invocation limit to the Queue ops/invocation limit which is the same number

Matt Silverlock•3/17/23, 7:08 PM

A KV put or an R2 put or a Queue send = each is "1"

Matt Silverlock•3/17/23, 7:08 PM

You can do any mix of those, up to 1000 per invocation - e.g. each time your queue()queue() is invoked on a batch of messages

kikaOP•3/17/23, 7:10 PM

lol, there's no sendBatch() for Rust

I m on paid unbound plan so 600ms should

Similar Threads

Similar Threads

Similar Threads