Performance Tip: Return Only Necessary Columns Using LINQ

re: Performance Tip: Return Only Necessary Columns Using LINQ

Cecil — Fri, 13 Jun 2008 14:00:47 GMT

True that works. Also if you're using a 3-tier approach, then returning anonymous types in your CRUD methods

is a lil different. Some I'd have to create an altered type to hold the small column set.

So For instance if I have a query that returns IEnumerable<Student>, I'd create a StudentAlt

class and return IEnumerable<StudentAlt>

public class FSEHS_STUDENT_MIN {

public string NSUID { get; set; }

public string FIRST_NAME { get; set; }

public string LAST_NAME { get; set; }

public override string ToString() {

return "NSUID: " + NSUID + "\nFirst Name :" + FIRST_NAME;

}

partial class FSEHS_STUDENT {

public static IEnumerable<STUDENTALT> select() {

SchoolDataContext db = new DataContext();

return from m in db.FSEHS_STUDENTs.Take(200) select new FSEHS_STUDENT_MIN{ FIRST_NAME=m.FIRST_NAME};

}

public static IEnumerable<STUDENT> select() {

SchoolDataContext db = new SchoolDataContext();

return from m in db.FSEHS_STUDENTs.Take(200)

select m;

}

re: Performance Tip: Return Only Necessary Columns Using LINQ

ZamesCurran — Wed, 11 Jun 2008 20:20:04 GMT

I'm told just creating an anonymous struct for the fields, instead of return the native LINQ object (even if it includes all of the columns) will speed things up, as the native object is dragging around a lot of extra weight (mainly there in case you update the object)

Performance Tip: Return Only Necessary Columns Using LINQ

Performance Tip: Return Only Necessary Columns Using LINQ — Wed, 11 Jun 2008 07:21:54 GMT

Pingback from Performance Tip: Return Only Necessary Columns Using LINQ