Linq to Sql Surprise Performance Hit

Loading...

Why not join our community?, there are 9 users online

home
linq
view story

DotNetKick.com is an open-source project. Please report any bugs and let us know your great suggestions. Currently running svn revision 620 (rss)

Kick Spy!, Kick Zeitgeist and Kick Widgets

29
kicks

Linq to Sql Surprise Performance Hit

published 7 months, 2 days ago, submitted by jconley 7 months, 7 days ago

jdconley.com — JD outlines a classic case of making assumptions while performance tuning. It turns out there are cases where Linq To SQL can take longer to compile a query than the round trip to SQL.

2 comments | category: Linq | Views: 0 | Get KickIt image code

tags: ToRead, Tuning, LINQ | tag it

Everyones tags:

Your tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

Anastasiosyal -

justin_etheredge -

offwhite - markheath - traskjd -

ColinCochrane - dkjariwala - zvikara -

johnrummell - rjdudley - JoHofmann -

brianjlowry - Loonquawl -

mdopp - csharpnjava - Reman - khushal999p -

stenbaek - braddunbar - munchr - trinity - buddydvd

Comments:

Excellent example of turning a performance-eating Linq query into a slim, compiled one, but he doesn't address why a simple application needs to hit the database over 1.1 million times just to load the page 3 times. That's crazy talk.

posted by jesse 7 months, 1 day ago

better be nice, he'z a h4x0r

posted by bladefist 6 months, 25 days ago

information

Login or create an account to comment on this story

Sponsored Link: www.carlist.ie

Search:

Ads via The Lounge

You are the editor:

View upcoming stories

Submit a story

How else can I help?

Earn money