Task and Parallel

This article explores the key distinctions between Parallel.ForEach and the Task family (specifically Task.WhenAll, Task.Run, etc.) in C#. Both facilitate concurrent or parallel code execution, but their applications, behaviors, and task handling differ significantly.

Parallel.ForEach:

Parallel.ForEach, a member of the System.Threading.Tasks namespace, enables parallel iteration over collections. It automatically distributes workload across available threads within the thread pool, proving highly efficient for CPU-bound operations.

Key Features:

• Parallel Execution: Iterations run concurrently on multiple threads.
• Thread Pool Reliance: It leverages the thread pool; you don't directly manage thread creation or lifespan.
• Synchronous Operation (Default): Execution blocks until the entire collection is processed.
• CPU-Bound Task Optimization: Best suited for CPU-intensive operations where threads operate independently.

Example:

using System;
using System.Threading.Tasks;

class Program
{
    static void Main(string[] args)
    {
        var items = new[] { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 };

        Parallel.ForEach(items, item =>
        {
            // Simulate CPU-intensive task (e.g., complex calculation)
            Console.WriteLine($"Processing item: {item} on thread {Task.CurrentId}");
        });

        Console.WriteLine("All items processed.");
    }
}

Tasks (Task.Run, Task.WhenAll):

Task.Run and Task.WhenAll offer granular control over asynchronous and parallel execution. While Task.Run can offload CPU-bound work, it's frequently paired with asynchronous code for I/O-bound tasks.

Key Features:

• Asynchronous Execution: Tasks primarily handle asynchronous programming, especially I/O-bound operations (network calls, database access).
• Task Management: Tasks are manually created, managed, and awaited (using Task.WhenAll, Task.WhenAny).
• Enhanced Flexibility: Tasks can be created and managed individually or in groups, providing fine-grained control.
• I/O-Bound Task Optimization: Although usable for CPU-bound tasks, Task.Run excels in scenarios requiring asynchronous behavior.

Example:

using System;
using System.Threading.Tasks;

class Program
{
    static void Main(string[] args)
    {
        var items = new[] { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 };

        Parallel.ForEach(items, item =>
        {
            // Simulate CPU-intensive task (e.g., complex calculation)
            Console.WriteLine($"Processing item: {item} on thread {Task.CurrentId}");
        });

        Console.WriteLine("All items processed.");
    }
}

---

Key Differences Summarized:

Feature

Parallel.ForEach

Task.Run / Task.WhenAll

Feature	Parallel.ForEach	Task.Run / Task.WhenAll
Primary Use Case	Parallel iteration for CPU-bound tasks.	Asynchronous and parallel execution (CPU/I/O).
Thread Control	Less control; uses the thread pool.	Full control over task creation and execution.
Execution Type	Synchronous (blocking).	Asynchronous (non-blocking unless awaited).
Task Type	CPU-bound tasks (parallel for loop).	General-purpose tasks (CPU-bound or I/O-bound).
Parallelism	Parallelism	Parallel or asynchronous.
Error Handling	Exceptions thrown per iteration.	Task.WhenAll aggregates exceptions.
Performance	Automatic performance tuning.	Manual task distribution management.

Primary Use Case

---

Parallel iteration for CPU-bound tasks.

Asynchronous and parallel execution (CPU/I/O).

Thread Control

Less control; uses the thread pool.

Full control over task creation and execution.

Execution Type

Synchronous (blocking).

Asynchronous (non-blocking unless awaited).

Task Type

CPU-bound tasks (parallel for loop).

General-purpose tasks (CPU-bound or I/O-bound).

Parallelism

Parallelism

Parallel or asynchronous.

Parallel.ForEachError Handling

Exceptions thrown per iteration.

aggregates exceptions.

Performance

Automatic performance tuning.

Manual task distribution management.

Choosing the Right Tool:

Use when:Task.RunTask.WhenAll

You have a CPU-bound task divisible into independent units of work.

• Automatic parallelization across multiple threads is desired.
• Synchronous execution is acceptable.

Use

---

/

when:

I/O-bound tasks are involved.Parallel.ForEach Task.RunGranular control over task management, cancellation, or synchronization is needed.Task.WhenAll

Combining parallelism and asynchrony is required. Conclusion: is excellent for straightforward CPU-bound tasks requiring minimal control. and provide greater flexibility, making them ideal for both CPU-bound and I/O-bound tasks, enabling the combination of concurrency and parallelism with fine-grained control.

The above is the detailed content of Task and Parallel. For more information, please follow other related articles on the PHP Chinese website!