Hi @Akshay Mahajan ,
Welcome to Microsoft Q&A platform and thanks for your query.
Yes, you are correct, if you leave the TTL to 0, ADF will always spawn a new Spark cluster environment for every Data Flow activity that executes. This means that an Azure Databricks cluster is provisioned each time and takes about ~4 minutes to become available and execute your job.
With the TTL feature, you only need to incur the cluster start-up on the first data flow activity execution. After that, we keep VMs available in a pool for the length of time of your TTL setting. And the subsequent data flow activities would still take ~1 min because you will still receive a new Spark context for each execution.
For example:
Without TTL : (Spin up 1 + Run 1) + (Spin up 2 + Run 2) + (Spin up 3 + Run 3) ...
(~4min + Job execution) + (~4min + Job execution) + (~4min + Job execution).....
With TTL : (Spin up a cluster + Run 1) + (Run 2) + (Run 3) ...
: (~4min + job execution) + (~1min +job execution) + (~1min +job execution)...
And to answer your question, yes if your Data flow activities are sequential then using TTL is the appropriate solution.
Additional info:
Please refer to below docs:
Hope this helps.
----------
Thank you
Please do consider to click on "Accept Answer" and "Upvote" on the post that helps you, as it can be beneficial to other community members.