EF6 two contexts vs. single context with two awaits(EF6 两个上下文与具有两个等待的单个上下文)
问题描述
以下哪一种是提高性能的更好方法?注意:对于某些操作,我最多可以执行五个独立的查询.
Which of these is a better approach for performance? Note: For some operations I have up to five independent queries to execute.
var foo = await context.foos.ToListAsync();
var bar = await context.bars.ToListAsync();
对比
var fooTask = context1.foos.ToListAsync();
var barTask = context2.bars.ToListAsync();
await Task.WhenAll(fooTask , barTask);
不用等待就使用相同的上下文会很棒,但 this answer 提到这是不可能的.
It would be great to use the same context without awaits, but this answer mentions that is not possible.
推荐答案
正如您所发现的,DbContext 不是线程安全的,因此真正并行运行查询的唯一选择是为每个线程创建一个新的 DbContext/任务.
As you found out, the DbContext is not thread safe, therefore the only option to really run the queries in parallel would be to create a new DbContext for each Thread/Task.
创建新 DbContext 的开销非常低.https://msdn.microsoft.com/en-us/library/cc853327.aspx
The overhead of creating a new DbContext is pretty low. https://msdn.microsoft.com/en-us/library/cc853327.aspx
由于对象将来自不同的 DbContext,为了进一步提高性能,我建议您也使用 NoTracking()
Since the object will come from different DbContexts and to further increase performance I recommend you also use NoTracking()
我用我拥有的数据库做了一个简单的测试程序:
I made a simple test program with a database I had:
class Program
{
public static void Main(string[] args)
{
Console.WriteLine("Warming up db context...");
using (var db = new TestDbContext())
{
Console.WriteLine(db.AuditLogItems.ToList().Count);
}
// 1st run
RunAsync();
RunTasked();
// 2nd run
RunAsync();
RunTasked();
Console.ReadKey();
}
private static void RunAsync()
{
Task.Run(async () =>
{
var sw = Stopwatch.StartNew();
List<AuditLogItem> list1;
List<AuditLogItem> list2;
using (var db = new TestDbContext())
{
list1 = await db.AuditLogItems.AsNoTracking().ToListAsync();
list2 = await db.AuditLogItems.AsNoTracking().ToListAsync();
}
sw.Stop();
Console.WriteLine("Executed {0} in {1}ms. | {2}", "Async", sw.ElapsedMilliseconds, list1.Count + " " + list2.Count);
}).Wait();
}
private static void RunTasked()
{
Func<List<AuditLogItem>> runQuery = () =>
{
using (var db = new TestDbContext())
{
return db.AuditLogItems.AsNoTracking().ToList();
}
};
var sw = Stopwatch.StartNew();
var task1 = Task.Run(runQuery);
var task2 = Task.Run(runQuery);
Task.WaitAll(task1, task2);
sw.Stop();
Console.WriteLine("Executed {0} in {1}ms. | {2}", "Tasked", sw.ElapsedMilliseconds, task1.Result.Count + " " + task2.Result.Count);
}
}
输出是:
Warming up db context...
5908
Executed Async in 293ms. | 5908 5908
Executed Tasked in 56ms. | 5908 5908
Executed Async in 194ms. | 5908 5908
Executed Tasked in 32ms. | 5908 5908
所以是的,选项 2 更快...
So yes, option 2 is faster...
这篇关于EF6 两个上下文与具有两个等待的单个上下文的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:EF6 两个上下文与具有两个等待的单个上下文
基础教程推荐
- 如何在 IDE 中获取 Xamarin Studio C# 输出? 2022-01-01
- 如何激活MC67中的红灯 2022-01-01
- SSE 浮点算术是否可重现? 2022-01-01
- rabbitmq 的 REST API 2022-01-01
- 将 Office 安装到 Windows 容器 (servercore:ltsc2019) 失败,错误代码为 17002 2022-01-01
- 有没有办法忽略 2GB 文件上传的 maxRequestLength 限制? 2022-01-01
- MS Visual Studio .NET 的替代品 2022-01-01
- 将 XML 转换为通用列表 2022-01-01
- c# Math.Sqrt 实现 2022-01-01
- 为什么Flurl.Http DownloadFileAsync/Http客户端GetAsync需要 2022-09-30