We have a bit of code that, in this example, ends up calling .OrderBy("SomeProperty ASC, SomeOtherProp DESC") a total of 262 times, each time on an EnumerableQuery<T> (that is, LINQ to objects rather than LINQ to sql).
With 1.0.8.18, the total CPU time spent in System.Linq.Dynamic.Core.DynamicQueryableExtensions::OrderBy was ~58ms. In 1.0.9, the total CPU time for the same code against the same data is ~17691ms:
It appears that System.Linq.Dynamic.Core is iterating over every single type currently loaded into the app domain, and pulling the custom attributes from every one of those types? Why is it doing this? Why does it do this on every single call to OrderBy()?
We have a bit of code that, in this example, ends up calling
.OrderBy("SomeProperty ASC, SomeOtherProp DESC")a total of 262 times, each time on anEnumerableQuery<T>(that is, LINQ to objects rather than LINQ to sql).With 1.0.8.18, the total CPU time spent in
System.Linq.Dynamic.Core.DynamicQueryableExtensions::OrderBywas ~58ms. In 1.0.9, the total CPU time for the same code against the same data is ~17691ms:It appears that System.Linq.Dynamic.Core is iterating over every single type currently loaded into the app domain, and pulling the custom attributes from every one of those types? Why is it doing this? Why does it do this on every single call to
OrderBy()?