Speed Up Skip and Take in Entity Framework with Lambda Expressions
If you're using Skip and Take in LINQ to page through your data, a tweak to your syntax can cut your response time by as much as 10 percent as you page through your data.
Imagine that you're paging through your SalesOrder data by repeatedly issuing this query that uses Skip and Take:
Const size As Integer = 10
Dim pos As Integer
Dim sos = db.SalesOrders.Skip(pos).Take(size)
pos += size
Every time you issue this query, you increment the pos variable by the amount in size to move to the "next" set of data.
If you were only executing this query once, the syntax used with Skip and Take is fine. If, however, you're executing the query multiple times (as you do when paging through data), then you're taking on some unnecessary overhead in your repeated queries.
The problem is that LINQ+Entity Framework has probably been creating a new query for every request because it's been inserting the values for pos and size as literals into the query. Instead of recycling the query (which really hasn't changed from one request to another), LINQ+EF has been re-analyzing the expression tree for your LINQ statement and submitting a new SQL statement on each request.
If you're using Entity Framework 6, then you can switch to using lambda expressions with Skip and Take. The benefit here is that LINQ+EF will now recognize your Skip and Take values as parameters that can be passed to a compiled query. The change looks like this in Visual Basic:
Dim sos = db.SalesOrders.Skip(Function() pos).Take(Function() size)
and like this in C#:
var sos = db.SalesOrders.Skip(() => pos).Take(() => size);
Now, LINQ+EF will compile your query once and just re-execute it on each request, passing the new values for pos and size. It's a trivial change to your syntax but it can shave 10 percent off the time it takes your repeated query to run.
Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter tweets about his VSM columns with the hashtag #vogelarticles. His blog posts on user experience design can be found at http://blog.learningtree.com/tag/ui/.