Understand parrallel execution of task by conductor server

[vidhi-pavan-agrawal]

I have made a Dynamic workflow where have I'm 50 HTTP tasks under forktask followed by a Fork_Join task where I'm combining all the 50 Tasks. I have installed Conductor version 2.32.0. and the default installation using docker-compose ("queues.dynomite.threads": "10"). As far as my understanding goes fork task will put all tasks in a scheduled state and then HTTP tasks being system tasks will be executed by the conductor server.
if we are willing to execute tasks parallelly where I should get a response time of the workflow = time taken by the longest task (approximately), How many HTTP tasks I can run parallelly with my configuration?

[vidhi-pavan-agrawal]

Also, how do I increase the capacity of the Conductor server to execute more number of HTTP Tasks in parallel?

[jxu-nflx]

Hello @vidhi-pavan-agrawal you can add this property to your config: conductor.app.system-task-max-poll-count. The default value is 1

[aravindanr]

You can also horizontally scale by adding more servers.