Automated Build Studio lets you organize macro operations so that you can execute them simultaneously. Automated Build Studio starts the next operation in a separate thread, without waiting for the previous operation to complete. This results in more efficient CPU usage and less macro execution time.

Below are sample situations where concurrent execution of operations can greatly improve performance:

• A macro is executed on a multiprocessor computer.
• The concurrent group includes tasks that do not depend on each other and do not share the same resources.
• The concurrent group includes operations that transmit data over the network, for example, operations of the FTP or HTTP categories. When running concurrently, the operations use separate connections.
• Long-running tasks in your macro are split into smaller concurrent tasks.
• The concurrent group includes a long-running operation that cannot be split into smaller operations. Within the concurrent group, the operation will be executed in parallel with other operations without blocking them, unlike within a serial group.

Almost all operations provided by Automated Build Studio can be run concurrently, as long as it does not break the macro logic and there are no technical limitations for the concurrent execution. To organize a concurrent group in your macro, you should place the desired operations to a Group operation’s children. Additionally, you can adjust properties of the concurrent group, such as the maximum number of threads that can be started by this group and the delay between starting a new thread:



The execution flow of this macro is shown in the following image: