为什么 LINQ JOIN 比 WHERE 链接快得多?
我最近升级到 VS 2010,并正在使用 LINQ to Dataset。我有一个用于授权的强类型数据集,位于 ASP.NET Web 应用程序的 HttpCache 中。
所以我想知道检查用户是否有权执行某些操作的最快方法实际上是什么。 这里是我的数据模型和一些如果有人感兴趣的话,还有其他信息。
我检查了 3 种方法:
- 直接数据库
- LINQ 查询,Where 条件作为“Join” - 语法
- LINQ 查询,Join - 语法
这些是结果每个函数调用 1000 次:
1.Iteration:
- 4,2841519 秒。
- 115,7796925 秒
- 2,024749 秒
2.迭代:
- 3,1954857 秒。
- 84,97047 秒
- 1,5783397 秒
3.迭代:
- 2,7922143 秒。
- 97,8713267 秒
- 1,8432163 秒
平均:
- 数据库:3,4239506333秒。
- 其中:99,5404964 秒。
- 加入:1,815435 秒。
为什么 Join 版本比 where 语法快得多,这使得它毫无用处,尽管作为 LINQ 新手,它似乎是最易读的。或者我在查询中遗漏了一些东西?
以下是 LINQ 查询,我跳过数据库:
Where:
Public Function hasAccessDS_Where(ByVal accessRule As String) As Boolean
Dim userID As Guid = DirectCast(Membership.GetUser.ProviderUserKey, Guid)
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule, _
roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule, _
role In Authorization.dsAuth.aspnet_Roles, _
userRole In Authorization.dsAuth.aspnet_UsersInRoles _
Where accRule.idAccessRule = roleAccRule.fiAccessRule _
And roleAccRule.fiRole = role.RoleId _
And userRole.RoleId = role.RoleId _
And userRole.UserId = userID And accRule.RuleName.Contains(accessRule)
Select accRule.idAccessRule
Return query.Any
End Function
Join:
Public Function hasAccessDS_Join(ByVal accessRule As String) As Boolean
Dim userID As Guid = DirectCast(Membership.GetUser.ProviderUserKey, Guid)
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule _
Join roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule _
On accRule.idAccessRule Equals roleAccRule.fiAccessRule _
Join role In Authorization.dsAuth.aspnet_Roles _
On role.RoleId Equals roleAccRule.fiRole _
Join userRole In Authorization.dsAuth.aspnet_UsersInRoles _
On userRole.RoleId Equals role.RoleId _
Where userRole.UserId = userID And accRule.RuleName.Contains(accessRule)
Select accRule.idAccessRule
Return query.Any
End Function
提前谢谢您。
编辑:在对两个查询进行一些改进以获得更有意义的性能值之后,JOIN 的优势甚至比以前大很多倍:
Join:
Public Overloads Shared Function hasAccessDS_Join(ByVal userID As Guid, ByVal idAccessRule As Int32) As Boolean
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule _
Join roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule _
On accRule.idAccessRule Equals roleAccRule.fiAccessRule _
Join role In Authorization.dsAuth.aspnet_Roles _
On role.RoleId Equals roleAccRule.fiRole _
Join userRole In Authorization.dsAuth.aspnet_UsersInRoles _
On userRole.RoleId Equals role.RoleId _
Where accRule.idAccessRule = idAccessRule And userRole.UserId = userID
Select role.RoleId
Return query.Any
End Function
Where< /strong>:
Public Overloads Shared Function hasAccessDS_Where(ByVal userID As Guid, ByVal idAccessRule As Int32) As Boolean
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule, _
roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule, _
role In Authorization.dsAuth.aspnet_Roles, _
userRole In Authorization.dsAuth.aspnet_UsersInRoles _
Where accRule.idAccessRule = roleAccRule.fiAccessRule _
And roleAccRule.fiRole = role.RoleId _
And userRole.RoleId = role.RoleId _
And accRule.idAccessRule = idAccessRule And userRole.UserId = userID
Select role.RoleId
Return query.Any
End Function
的结果(在速度更快的计算机上)
- 1000 次调用 2. 其中
1.迭代:
- 0,0713669 秒。
- 12,7395299 秒
2.迭代:
- 0,0492458 秒。
- 12,3885925 秒
3.迭代:
- 0,0501982 秒。
- 13,3474216 秒
平均:
- 加入:0,0569367 秒。
- 其中:12,8251813 秒。
Join 速度提高了 225 倍
结论:避免在 WHERE 中指定关系并尽可能使用 JOIN(绝对是在 LINQ to DataSet 和 Linq-To-Objects
一般来说)。
I've recently upgraded to VS 2010 and am playing around with LINQ to Dataset. I have a strong typed dataset for Authorization that is in HttpCache of an ASP.NET WebApplication.
So i wanted to know what actually is the fastest way to check if a user is authorized to do something. Here is my datamodel and some other informations if somebody is interested.
I have checked 3 ways:
- direct database
- LINQ query with Where conditions as "Join" - Syntax
- LINQ query with Join - Syntax
These are the results with 1000 calls on each function:
1.Iteration:
- 4,2841519 sec.
- 115,7796925 sec.
- 2,024749 sec.
2.Iteration:
- 3,1954857 sec.
- 84,97047 sec.
- 1,5783397 sec.
3.Iteration:
- 2,7922143 sec.
- 97,8713267 sec.
- 1,8432163 sec.
Average:
- Database: 3,4239506333 sec.
- Where: 99,5404964 sec.
- Join: 1,815435 sec.
Why is the Join-version so much faster than the where-syntax which makes it useless although as a LINQ newbie it seems to be the most legible. Or have i missed something in my queries?
Here are the LINQ queries, i skip the database:
Where:
Public Function hasAccessDS_Where(ByVal accessRule As String) As Boolean
Dim userID As Guid = DirectCast(Membership.GetUser.ProviderUserKey, Guid)
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule, _
roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule, _
role In Authorization.dsAuth.aspnet_Roles, _
userRole In Authorization.dsAuth.aspnet_UsersInRoles _
Where accRule.idAccessRule = roleAccRule.fiAccessRule _
And roleAccRule.fiRole = role.RoleId _
And userRole.RoleId = role.RoleId _
And userRole.UserId = userID And accRule.RuleName.Contains(accessRule)
Select accRule.idAccessRule
Return query.Any
End Function
Join:
Public Function hasAccessDS_Join(ByVal accessRule As String) As Boolean
Dim userID As Guid = DirectCast(Membership.GetUser.ProviderUserKey, Guid)
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule _
Join roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule _
On accRule.idAccessRule Equals roleAccRule.fiAccessRule _
Join role In Authorization.dsAuth.aspnet_Roles _
On role.RoleId Equals roleAccRule.fiRole _
Join userRole In Authorization.dsAuth.aspnet_UsersInRoles _
On userRole.RoleId Equals role.RoleId _
Where userRole.UserId = userID And accRule.RuleName.Contains(accessRule)
Select accRule.idAccessRule
Return query.Any
End Function
Thank you in advance.
Edit: after some improvements on both queries to get more meaningful perfomance-values, the advantage of the JOIN is even many times greater than before:
Join:
Public Overloads Shared Function hasAccessDS_Join(ByVal userID As Guid, ByVal idAccessRule As Int32) As Boolean
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule _
Join roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule _
On accRule.idAccessRule Equals roleAccRule.fiAccessRule _
Join role In Authorization.dsAuth.aspnet_Roles _
On role.RoleId Equals roleAccRule.fiRole _
Join userRole In Authorization.dsAuth.aspnet_UsersInRoles _
On userRole.RoleId Equals role.RoleId _
Where accRule.idAccessRule = idAccessRule And userRole.UserId = userID
Select role.RoleId
Return query.Any
End Function
Where:
Public Overloads Shared Function hasAccessDS_Where(ByVal userID As Guid, ByVal idAccessRule As Int32) As Boolean
Dim query = From accRule In Authorization.dsAuth.aspnet_AccessRule, _
roleAccRule In Authorization.dsAuth.aspnet_RoleAccessRule, _
role In Authorization.dsAuth.aspnet_Roles, _
userRole In Authorization.dsAuth.aspnet_UsersInRoles _
Where accRule.idAccessRule = roleAccRule.fiAccessRule _
And roleAccRule.fiRole = role.RoleId _
And userRole.RoleId = role.RoleId _
And accRule.idAccessRule = idAccessRule And userRole.UserId = userID
Select role.RoleId
Return query.Any
End Function
Result for 1000 calls (on a faster computer)
- Join | 2. Where
1.Iteration:
- 0,0713669 sec.
- 12,7395299 sec.
2.Iteration:
- 0,0492458 sec.
- 12,3885925 sec.
3.Iteration:
- 0,0501982 sec.
- 13,3474216 sec.
Average:
- Join: 0,0569367 sec.
- Where: 12,8251813 sec.
Join is 225 times faster
Conclusion: avoid WHERE to specify relations and use JOIN whenever possible(definitely in LINQ to DataSet and Linq-To-Objects
in general).
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
您的第一种方法(数据库中的 SQL 查询)非常有效,因为数据库知道如何执行联接。但将其与其他方法进行比较并没有什么意义,因为它们直接在内存中工作(Linq to DataSet)
具有多个表和
Where
条件的查询实际上执行 < em>所有表的笛卡尔积,然后过滤满足条件的行。这意味着对每个行组合 (n1 * n2 * n3 * n4) 评估Where
条件Join
运算符从第一个表中获取行,然后仅获取第二个表中具有匹配键的行,然后仅获取第三个表中具有匹配键的行,依此类推。这样效率更高,因为它不需要执行那么多操作Your first approach (SQL query in the DB) is quite efficient because the DB knows how to perform a join. But it doesn't really make sense to compare it with the other approaches, since they work directly in memory (Linq to DataSet)
The query with multiple tables and a
Where
condition actually performs a cartesian product of all the tables, then filters the rows that satisfy the condition. This means theWhere
condition is evaluated for each combination of rows (n1 * n2 * n3 * n4)The
Join
operator takes the rows from the first tables, then takes only the rows with a matching key from the second table, then only the rows with a matching key from the third table, and so on. This is much more efficient, because it doesn't need to perform as many operationsJoin
速度要快得多,因为该方法知道如何组合表以将结果缩减为相关组合。当您使用Where
指定关系时,它必须创建每种可能的组合,然后测试条件以查看哪些组合是相关的。Join
方法可以设置一个哈希表作为索引来快速将两个表压缩在一起,而Where
方法在所有组合都已创建后运行,因此它不能使用任何技巧来预先减少组合。The
Join
is much faster, because the method knows how to combine the tables to reduce the result to the relevant combinations. When you useWhere
to specify the relation, it has to create every possible combination, and then test the condition to see which combinations are relevant.The
Join
method can set up a hash table to use as an index to quicky zip two tables together, while theWhere
method runs after all the combinations are already created, so it can't use any tricks to reduce the combinations beforehand.您真正需要知道的是为这两个语句创建的 sql。有几种方法可以实现这一点,但最简单的是使用 LinqPad。查询结果正上方有几个按钮,将更改为 sql。这将为您提供比其他任何东西更多的信息。
不过你在那里分享的信息很好。
what you really need to know is the sql that was created for the two statements. There are a few ways of getting to it but the simplest is to use LinqPad. There are several buttons right above the query results that will change to the sql. That will give you a lot more information than anything else.
Great information you shared there though.