【发布时间】:2021-06-01 17:44:57
【问题描述】:
我想出了以下代码,它以 5 的页面大小重复调用数据库分页函数,并为页面中的每个项目并行执行一个函数,最大并发数为 4。它看起来像它到目前为止工作但我不确定是否需要使用锁定来封闭parallelInvocationTasks.Remove(completedTask); 行和Task.WhenAll(parallelInvocationTasks.ToArray()); 那么我需要在此处使用锁定吗?您是否看到任何其他改进?
这是代码
程序.cs
using System;
using System.Collections.Generic;
using System.Threading;
using System.Threading.Tasks;
namespace ConsoleApp1
{
class Program
{
private static async Task Main(string[] args)
{
Console.WriteLine("Starting");
Func<int, int, CancellationToken, Task<IList<string>>> getNextPageFunction = GetNextPageFromDatabase;
await getNextPageFunction.ForEachParallel(4, 5, new CancellationToken(), async (item) =>
{
Console.WriteLine($"{item} started");
//simulate processing
await Task.Delay(1000);
Console.WriteLine($"{item} ended");
});
Console.WriteLine("Done");
}
private static async Task<IList<string>> GetNextPageFromDatabase(
int offset,
int pageSize,
CancellationToken cancellationToken)
{
//simulate i/o and database paging
await Task.Delay(2000, cancellationToken);
var pageData = new List<string>();
//simulate just 4 pages
if (offset >= pageSize * 3)
{
return pageData;
}
for (var i = 1; i <= pageSize; i++)
{
string nextItem = $"Item {i + offset}";
pageData.Add(nextItem);
}
return pageData;
}
}
}
PagingExtensions.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading;
using System.Threading.Tasks;
namespace ConsoleApp1
{
public static class PagingExtensions
{
public static async Task<int> ForEachParallel<TItem>(
this Func<int, int, CancellationToken, Task<IList<TItem>>> getNextPageFunction,
int concurrency,
int pageSize,
CancellationToken cancellationToken,
Func<TItem, Task> forEachFunction)
{
var enumeratedCount = 0;
if (getNextPageFunction == null || forEachFunction == null)
{
return enumeratedCount;
}
var offset = 0;
using (var semaphore = new SemaphoreSlim(concurrency))
{
IList<Task> parallelInvocationTasks = new List<Task>();
IList<TItem> items;
do
{
items = await getNextPageFunction(offset, pageSize, cancellationToken) ?? new List<TItem>();
foreach (TItem item in items)
{
await semaphore.WaitAsync(cancellationToken);
Task forEachFunctionTask = Task.Factory.StartNew(async () =>
{
try
{
await forEachFunction(item);
}
finally
{
// ReSharper disable once AccessToDisposedClosure
// This is safe as long as Task.WhenAll is called before the using semaphore
// enclosure ends
semaphore.Release();
}
}, cancellationToken)
.Unwrap();
parallelInvocationTasks.Add(forEachFunctionTask);
#pragma warning disable 4014
forEachFunctionTask.ContinueWith((completedTask) =>
#pragma warning restore 4014
{
if (completedTask.Exception == null)
{
//Intention is to release completed tasks during enumeration as they complete
//so they can be GCed. This is to ensure the 'parallelInvocationTasks' list does not
//grow in an unmanaged manner resulting in a list holding multiple completed tasks
//unnecessarily consuming more memory with each added invocation task
//Thus the final Task.WhenAll call below will only need to await only faulted tasks
//causing it to throw an exception and/or a minimal list of incomplete tasks only
parallelInvocationTasks.Remove(completedTask);
}
}, cancellationToken);
enumeratedCount += 1;
}
offset += pageSize;
}
while (items.Count >= pageSize);
await Task.WhenAll(parallelInvocationTasks.ToArray());
}
return enumeratedCount;
}
}
}
【问题讨论】:
-
您是否有意将
await semaphore.WaitAsync(cancellationToken);放在任务之外,而将semaphore.Release();放在ForEachParallel()中创建的任务中?通常你会放置这些,以便它们在同一个线程(任务)上执行 -
parallelInvocationTasks.Remove(completedTask);绝对应该有一个lock,任何时候你可能修改一个集合,即使是用这样的方法捕获的,你应该在修改它时锁定它. -
@JonasH Parallel.ForEach 用于 CPU 密集型计算,不识别异步方法。它不会等待他们 AFAIK
-
绝对是!我只是澄清一下。你第一次写的时候我就在那儿:P。我只是发现信号量很重要,如果有意使用该技术 - 因为如果实施不当,它是导致不匹配版本的少数几种方法之一。
-
Harindaka 是的,使用 TPL 数据流,您将获得更好的异常处理行为。基本上一个失败的任务会导致整个并行循环的及时失败,而不是等待所有其他任务完成才在最后收到这个错误。 I have posted myself 链接问题中基于 TPL 数据流的
ForEachAsync方法的一些简单实现。
标签: c# asynchronous parallel-processing locking task