การทำงานแบบขนานและการกำหนดค่า

Imagine you have several independent tasks that need to be done. If you do them one by one, it takes a long time. But what if you could do some of them at the same time?

This is the core idea behind parallel execution in Gradle. It allows Gradle to run multiple independent tasks simultaneously, which can significantly reduce your overall build time, especially for large projects or multi-project builds.

Gradle's parallel execution is not enabled by default. You need to explicitly tell Gradle to use it. There are two main ways to activate it:

• Command Line: Use the --parallel (or -P) option when running Gradle commands.
• Configuration File: Add org.gradle.parallel=true to your project's gradle.properties file.

Using the command line option overrides the setting in gradle.properties.

Let's look at a simple build.gradle file defining two independent tasks. Normally, running gradle longTaskA longTaskB would take about 4 seconds (2s + 2s).

However, if you run gradle longTaskA longTaskB --parallel, Gradle will attempt to run both tasks at the same time. On a machine with enough CPU cores, this build would complete in roughly 2 seconds!

How does Gradle know which tasks can run in parallel? It builds a Directed Acyclic Graph (DAG) of all tasks and their dependencies.

Tasks that have no dependencies on each other, or whose dependencies have already been satisfied, are considered independent. Gradle's parallel executor identifies these independent branches in the DAG and schedules them to run concurrently.

Benefits of Parallel Execution:

• Faster Builds: Reduces overall build time, especially for projects with many independent modules or tasks.
• Efficient Resource Use: Leverages multi-core processors more effectively.

Considerations:

• Overhead: Managing parallel threads has a slight overhead.
• Resource Contention: If tasks compete for the same resources (e.g., I/O, network), performance might not improve or could even degrade.
• Dependencies: Tasks with dependencies still run sequentially.

While --parallel enables parallel execution, you can also control the maximum number of worker threads Gradle uses. This is done via the org.gradle.workers.max property.

By default, Gradle uses a number of workers equal to the number of CPU cores available on your machine. You might want to adjust this if your tasks are I/O-bound rather than CPU-bound, or if you want to reserve CPU resources for other applications.

You can set the maximum number of parallel workers in your gradle.properties file. This example limits Gradle to using at most 2 worker threads, even if your machine has more CPU cores.

Experimenting with this value can help you find the optimal balance for your specific project and hardware configuration.

Parallel execution is powerful, but it's not a silver bullet. There are scenarios where it might not be beneficial or could even cause issues:

• Shared Resources: If tasks write to the same file or modify shared state concurrently.
• Limited Resources: On machines with very few CPU cores or limited RAM, the overhead might outweigh the benefits.
• Small Builds: For projects with very few tasks or short build times, the setup overhead can make builds slightly slower.
• Intermittent Failures: If tasks occasionally fail only when running in parallel, it often indicates a hidden dependency or race condition.

If you encounter issues with parallel builds, here are some tips:

• Use --info or --debug: These flags provide more verbose output, helping you see which tasks are running and when.
• Look for "parallel": Confirm that Gradle is indeed attempting parallel execution in the logs.
• Isolate Issues: Temporarily disable parallel execution with --no-parallel to determine if the issue is specific to parallel mode.
• Check Dependencies: Ensure all task dependencies are correctly declared to prevent unexpected behavior.

Let's test your understanding of Gradle's parallel execution.

In this lesson, you learned about Gradle's parallel execution, a powerful feature for optimizing build performance. We covered:

• How to enable parallel builds using --parallel or gradle.properties.
• How Gradle uses its task graph to determine which tasks can run concurrently.
• The benefits and potential drawbacks of using parallel execution.
• Configuring the maximum number of worker threads with org.gradle.workers.max.
• Scenarios where parallel execution might not be ideal and tips for troubleshooting.

By intelligently using parallel execution, you can significantly reduce your build times and improve developer productivity!