Just want to clarify something about Cloud concurr...
# ask-community
c
Just want to clarify something about Cloud concurrency: even if you have multiple agents, the ability to run tasks is still hard limited by the concurrency limit correct?
k
Hey @Charles Liu, Yes - if you set tags on the tasks you’d like to limit, this will apply to all TaskRuns across your entire tenant, across all Agents. Let me know if I can clarify, in case you may be referring to something else!
c
Ah right. I did have a question similar to that but I believe I've resolved it for now. I meant run concurrency slots, if it's not too much trouble!
For some context: I'm working on load testing our EKS setup, and short of converting a huge legacy pipeline (not time efficient in my scenario) I was hoping to trigger the ones I have already converted to see if I can kick off auto-scaling but having two slots prevents me from cracking 50% utilization on my EC2.
k
And to be clear - you’re referring to two Prefect Cloud concurrency slots, correct?
c
Yup that's correct!
👍 1
k
No problem, thanks for clarifying. Right now there are two offerings for Cloud: the older model is limited by the number of concurrently running FlowRuns at a given time (depending on your service tier), and the newer model with no FlowRun concurrency limitations but instead allocates the number of successful Task Runs you can execute. Importantly, both of these models do not limit the number of Tasks you can run at a given time unless otherwise configured by tags as mentioned. So you could upgrade your tenant to accommodate more concurrency slots, but it may be better just to move over to the new successful Task Run model. If you’d like to test that out, I can have someone reach out to you to change your tenant for testing (you may even be able to self-serve to the new model, but I’ll have to double-check). Let me know what you think.
c
This is a discussion I would need to have internally so I'll pass along the information. Thanks, and I'll get back to y'all!
👍 1