Re: Is LINQ consumes double the time of Traditional Data Connection?
- From: Jon Skeet [C# MVP] <skeet@xxxxxxxxx>
- Date: Tue, 4 Sep 2007 22:43:27 +0100
Chakravarthy <dskcheck@xxxxxxxxx> wrote:
<snip>
For your attention here comes the result for the first execution time of
each method
I've only just spotted the word "first" in here.
What about the next time you execute the query? On my box, that's much,
much faster. This makes sense - not only has LINQ got to connect to the
database (like the DataAdapter does) but it's also got to build an
assembly. That assembly can be reused for subsequent queries, however.
Try measuring the subsequent executions of the same query and I'm sure
you'll see a big difference.
How much do you care about losing a tenth of a second or so of
performance *once* (per run) compared with the *huge* benefit in
development effort that LINQ will bring?
--
Jon Skeet - <skeet@xxxxxxxxx>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
.
- References:
- Is LINQ consumes double the time of Traditional Data Connection?
- From: Chakravarthy
- Is LINQ consumes double the time of Traditional Data Connection?
- Prev by Date: Re: regex replace problem.
- Next by Date: Re: SQL Server does not DELETE rows for real
- Previous by thread: Re: Is LINQ consumes double the time of Traditional Data Connectio
- Next by thread: Progress bar control in System tray
- Index(es):
Relevant Pages
|
Loading
