我目前使用Entity Framework Core,并且效果很好。但是,我要在应用程序中尝试优化的一件事是在查询时从数据库返回计算数据。我首先使用代码,其中每个模型都直接映射到其中的单个表。
这是我的持久性模型的简化示例:
public class User
{
public int Id { get; set; }
public string Name { get; set; }
public ICollection<UserRole> Roles { get; set; }
}
public class UserRole
{
public int Id { get; set; }
public int UserId { get; set; }
public User User { get; set; }
public string Role { get; set; }
}
我当前使用的是规范模式的一种变体,它使我能够在执行之前对查询运行可变数量的.Include / .ThenInclude
。但是,我想做的是有条件地启用投影的特定部分。
例如,以下是我的域模型的显示方式:
public class UserImpl
{
public User User { get; set; }
public int? RoleCount { get; set; }
public static Expression<Func<User, UserImpl>> Projection(UserImplParams opts) {
return u => new UserImpl
{
User = u,
RoleCount = opts != null && opts.IncludeRoleCount ? u.Roles.Count() : default(int?)
};
}
}
public class UserImplParams
{
public bool IncludeRoleCount { get; set; }
}
我想实现的目标是一种与此类似的方式:
var opts= new UserImplParams
{
IncludeUserRole = true
};
await _databaseContext.Users.Select(UserImpl.Projection(opts)).ToListAsync();
我想让EF Core EITHER看到:
u => new UserImpl
{
User = u,
RoleCount = u.Roles.Count()
};
OR
u => new UserImpl
{
User = u,
RoleCount = default(int?)
};
有可能吗?这主要是因为此表达式可能包含多个投影属性,甚至包含嵌套的投影属性。每次只将少量数据全部发射到数据库中似乎效率低下。
答案 0 :(得分:0)
[EDIT]我在我的网站上发布了此代码的最新版本 https://eliottrobson.me/entity-framework-core-projection-performance/ 基本上是相同的,但是增加了对更多方案的支持。
之所以这样做,部分原因是过早的优化。我敢肯定,在90%的情况下,如果CASE值为1 = 1或1 = 0(对于true和false),则发送大型SQL将会得到正确的优化。但是,事实是CASE语句并不总是会使https://dba.stackexchange.com/questions/12941/does-sql-server-read-all-of-a-coalesce-function-even-if-the-first-argument-is-no/12945#12945短路。
事不宜迟,这是我如何实现此目标的解决方案。
主要功能位于该新类中:
public class ProjectionExpressionVisitor : ExpressionVisitor
{
internal Expression<Func<TSource, TDest>> Optimise<TSource, TDest>(Expression<Func<TSource, TDest>> expression)
{
return Visit(expression) as Expression<Func<TSource, TDest>>;
}
protected override Expression VisitConditional(ConditionalExpression node)
{
var test = ReduceExpression(node.Test);
// The conditional is now a constant, we can replace the branch
if (test is ConstantExpression testNode)
{
var value = (dynamic) testNode.Value;
return value ? ReduceExpression(node.IfTrue) : ReduceExpression(node.IfFalse);
}
// If it is not a conditional, we follow the default behaviour
return base.VisitConditional(node);
}
public Expression ReduceExpression(Expression node)
{
if (node is ConstantExpression)
{
// Constants represent the smallest item, so we can just return it
return node;
}
else if (node is MemberExpression memberNode)
{
return ReduceMemberExpression(memberNode);
}
else if (node is BinaryExpression binaryNode)
{
return ReduceBinaryExpression(binaryNode);
}
// This is not a supported expression type to reduce, fallback to default
return node;
}
public Expression ReduceMemberExpression(MemberExpression node)
{
if (
node.Expression.NodeType == ExpressionType.Constant ||
node.Expression.NodeType == ExpressionType.MemberAccess
)
{
var objectMember = Expression.Convert(node, typeof(object));
var getterLambda = Expression.Lambda<Func<object>>(objectMember);
var getter = getterLambda.Compile();
var value = getter();
return Expression.Constant(value);
}
return node;
}
public Expression ReduceBinaryExpression(BinaryExpression node)
{
var left = ReduceExpression(node.Left);
var right = ReduceExpression(node.Right);
var leftConst = left as ConstantExpression;
var rightConst = right as ConstantExpression;
// Special optimisations
var optimised = OptimiseBooleanBinaryExpression(node.NodeType, leftConst, rightConst);
if (optimised != null) return Expression.Constant(optimised);
if (leftConst != null && rightConst != null)
{
var leftValue = (dynamic)leftConst.Value;
var rightValue = (dynamic)rightConst.Value;
switch (node.NodeType)
{
case ExpressionType.Add:
return Expression.Constant(leftValue + rightValue);
case ExpressionType.Divide:
return Expression.Constant(leftValue / rightValue);
case ExpressionType.Modulo:
return Expression.Constant(leftValue % rightValue);
case ExpressionType.Multiply:
return Expression.Constant(leftValue * rightValue);
case ExpressionType.Power:
return Expression.Constant(leftValue ^ rightValue);
case ExpressionType.Subtract:
return Expression.Constant(leftValue - rightValue);
case ExpressionType.And:
return Expression.Constant(leftValue & rightValue);
case ExpressionType.AndAlso:
return Expression.Constant(leftValue && rightValue);
case ExpressionType.Or:
return Expression.Constant(leftValue | rightValue);
case ExpressionType.OrElse:
return Expression.Constant(leftValue || rightValue);
case ExpressionType.Equal:
return Expression.Constant(leftValue == rightValue);
case ExpressionType.NotEqual:
return Expression.Constant(leftValue != rightValue);
case ExpressionType.GreaterThan:
return Expression.Constant(leftValue > rightValue);
case ExpressionType.GreaterThanOrEqual:
return Expression.Constant(leftValue >= rightValue);
case ExpressionType.LessThan:
return Expression.Constant(leftValue < rightValue);
case ExpressionType.LessThanOrEqual:
return Expression.Constant(leftValue <= rightValue);
}
}
return node;
}
private bool? OptimiseBooleanBinaryExpression(ExpressionType type, ConstantExpression leftConst, ConstantExpression rightConst)
{
// This is only a necessary optimisation when only part of the binary expression is constant
if (leftConst != null && rightConst != null)
return null;
var leftValue = (dynamic)leftConst?.Value;
var rightValue = (dynamic)rightConst?.Value;
// We can check for constants on each side to simplify the reduction process
if (
(type == ExpressionType.And || type == ExpressionType.AndAlso) &&
(leftValue == false || rightValue == false))
{
return false;
}
else if (
(type == ExpressionType.Or || type == ExpressionType.OrElse) &&
(leftValue == true || rightValue == true))
{
return true;
}
return null;
}
}
从根本上说,我们的想法是通过尽可能减少条件表达式来优化条件表达式,然后在混合参数lambda时应用一些特殊情况的逻辑。
用法如下
var opts = new UserImplParams
{
IncludeUserRole = true
};
var projection = UserImpl.Projection(opts);
var expression = new ProjectionExpressionVisitor().Optimise(projection);
await _databaseContext.Users.Select(expression).ToListAsync();
希望这会帮助遇到类似问题的其他人。
答案 1 :(得分:-1)
您可以先有条件地更改组名(在第一个选择中),然后再重新组,
现在你有两种类型的组
.GroupBy(x => new {x.Brand})
.Select(x => new DisputeReportListModel
{
Amount = x.Sum(y => y.Amount),
Scheme = _isMastercard(x.Key.Brand) ? "MASTERCARD" : "VISA",
}).AsEnumerable()
.GroupBy(x => new {x.Scheme})
.Select(x => new DisputeReportListModel
{
Amount = x.Sum(y => y.Amount),
Scheme = x.Key.Scheme
})
.ToList();