Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

max_burst_size and bucket_size in taskqueues

Hi people!

TusharAgarwal_1-1721310815430.png

These are my queue configurations.

I have configured my queues to run as slowly as possible by setting max_concurrent_requests to 1 and rate to 1/s. However, due to the bucket_size and max_burst_size settings, tasks are still being executed quickly, despite the rate limit I set.

Can I set the bucket_size to 1 to meet my requirements? Are there any potential error scenarios that could arise from making this change?

1 REPLY 1

Hi @TusharAgarwal,

Welcome to Google Cloud Community!

Short answer is both YES and NO depending on what you are using. I don’t think there's any repercussions when setting it to 1 as long as it satisfies your use case. But keep in mind that we recommend using the default or higher value if you have a lot of queued tasks.

YES: Setting the bucket_size is possible for App Engine queues that were created or updated using queue.yaml.

bucketsize.png

You can also slow it down by changing the rate to either 1/m, 1/h or 1/d.

rate.png

NOIf creating a queue from Console > Cloud Tasks or via Cloud Tasks API.

    • Don’t have the option to manually set “Max burst size”.

Hope this clarifies your concern.