Does making an async call from task activity, release the task hub worker, similar to C# releasing the thread

[bbala-github]

As per my understanding when an async call is made in C#, the calling thread is released for other work. When the async call completes, another worker thread is used to resume execution.

Similarly, when a remote async call is made from a task hub worker task-activity, is the worker blocked till the remote call completes or is it available for other task execution? If it is the former, are there any challenges wrt releasing it for other work. It is possible that the workers may exhausted when the original action completes, but that is a generic problem, execution has to wait till a worker is available.

Please let me know your thoughts. Thanks.

[cgillum]

Similarly, when a remote async call is made from a task hub worker task-activity, is the worker blocked till the remote call completes or is it available for other task execution?

Each activity function is internally triggered by a worker thread from the .NET thread pool, so one activity's execution will never block another activity's execution. Many activities can be run in parallel, up to the configured maximum concurrency limit. Documentation on concurrency limits can be found here.

[bbala-github]

Ok, thanks for the response.

I got confused since I was expecting a task hub worker is similar to a thread, and to achieve parallelism we need to create multiple 'workers', which is analogous to a thread pool. Based on your response and documentation, it seems that is not the case. A worker internally uses a thread pool and can run upto configured max concurrency limit, this makes sense.

Essentially, we only need to instantiate 1 task hub worker (per task hub, per instance/process) and configure max concurrency limit as needed. Correct me if my understanding is incorrect.

[cgillum]

Yes, that's correct.