[ By popular demand, here are links for all 5 parts in the
series Part 1, Part 2, Part 3, Part 4, Part 5   -Rico ]  I love
Linq.  Really.  That might scare you because it has all these
wacky new constructs and as a performance guy you'd think that
I'd be all about getting rid of abstractions and just getting to
the metal.  But don't be scared, I haven't lost my mind.  Linq
is great because, even though it adds some levels of complexity,
it simulataneously increases the chunkiness of the work that the
framework receives in such a way that it creates fantastic
opportunities to deliver performance.  Just like SQL can do a
great job optimizing database queries because they are chunky
enough.  And speaking of databases, DLinq is really where the
opportunities for amazing coolness are present.  I first started
looking at the performance of DLinq (it's officially called Linq
to SQL but I still call it DLinq)shortly after the May 2006 CTP
-- the very same one many of you are still using.  There were
some great opport