Is LINQ consumes double the time of Traditional Data Connection?

[=?Utf-8?B?Q2hha3JhdmFydGh5?=]

Today, after watching the presentation by Amanda Silver at
http://channel9.msdn.com/Showpost.aspx?postid=335058 , from Channel 9,
started exploring the LINQ features. Surprisingly, few facts unearthed to
prove that LINQ is slower, much to double the time consumed by the usage of
traditional Data Adapter. Correct me if you find these facts can be proved
fault

HW Scenario :
----------------------------------------------------------------------------
System OS - XP Prof with SP2
System Processor - AMD 3000+ with 2GHz
RAM - 1 GB
DB Server - LocalHost on SQL Server 2005
Implemented with Orcas Beta 2
----------------------------------------------------------------------------

Source Code copied from Amanda's presentation

Code Snippet for LINQ
----------------------------------------------------------------------------
Dim t1, t2 As Double

t1 = Date.Now.TimeOfDay.TotalMilliseconds

Dim db As New exLinqDataContext(My.Settings.NorthwindConnectionS tring)

Dim query = From cust In db.Customers _

Join sup In db.Suppliers _

On cust.City Equals sup.City _

Select cust.CompanyName, sup.ContactName, cust.City

Me.DataGridView1.DataSource = query

t2 = Date.Now.TimeOfDay.TotalMilliseconds

Dim diffT As Double

diffT = t2 - t1

MessageBox.Show(diffT)
----------------------------------------------------------------------------
Source Code using Traditional Data Adapter
----------------------------------------------------------------------------
Dim t1, t2 As Double

t1 = Date.Now.TimeOfDay.TotalMilliseconds

Dim cn As New SqlClient.SqlConnection("Data Source=localhost;Initial
Catalog=Northwind;Integrated Security=True")

Dim da As New SqlClient.SqlDataAdapter("Select
C.CompanyName,S.ContactName,C.City from Customers C,Suppliers S Where C.City
= S.City", cn)

Dim DS As New DataSet

da.Fill(DS)

GV.DataSource = DS.Tables(0)

t2 = Date.Now.TimeOfDay.TotalMilliseconds

Dim diffT As Double

diffT = t2 - t1

MessageBox.Show(diffT)
----------------------------------------------------------------------------

For your attention here comes the result for the first execution time of
each method

-------------------
LINQ DataAdapter
-------------------
171.875 93.750
171.875 93.750
156.250 78.125
156.250 78.125
156.250 78.125
-------------------

Can some one help me to understand to interpret the results and how LINQ is
advantageous than the tradtional way of using Data Adapter with Data
Connections

--
Every thing is perfect, as long as you share!!!

Don''t forget to rate the post

[Jon Skeet [C# MVP]]

Chakravarthy <ds******@india.comwrote:

<snip>

Can some one help me to understand to interpret the results and how LINQ is
advantageous than the tradtional way of using Data Adapter with Data
Connections

Have you looked at the SQL query being used? Those figures are pretty
odd... normally LINQ should be "about" as fast as traditional methods,
so long as the query is equivalent.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?Q2hha3JhdmFydGh5?=]

Jon,

Yes, what you said is correct from the point of statements given by the
representatives as well as by the company, Microsoft's official barriers. But
unfortunately, the figures doesn't lie. Am really surprised to see such kind
of figures specially using the latest framework version.

Secondly, i guess there is nothing wrong in the SQL Query. Correct me if am
found fault.

Anyhow, thanks for replying.
--
Every thing is perfect, as long as you share!!!

Don''t forget to rate the post
"Jon Skeet [C# MVP]" wrote:

Chakravarthy <ds******@india.comwrote:

<snip>

Can some one help me to understand to interpret the results and how LINQ is
advantageous than the tradtional way of using Data Adapter with Data
Connections

Have you looked at the SQL query being used? Those figures are pretty
odd... normally LINQ should be "about" as fast as traditional methods,
so long as the query is equivalent.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Chakravarthy <ds******@india.comwrote:

Yes, what you said is correct from the point of statements given by the
representatives as well as by the company, Microsoft's official barriers. But
unfortunately, the figures doesn't lie.

Benchmarks can very, very easily be wrong. Benchmarking is really quite
tricky to get right.

Am really surprised to see such kind
of figures specially using the latest framework version.

Secondly, i guess there is nothing wrong in the SQL Query. Correct me if am
found fault.

You haven't told us what the query generated by LINQ is. That's what I
was asking before.

If you could produce a short but *complete* program, we could test it
for ourselves, of course.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Chakravarthy <ds******@india.comwrote:

<snip>

For a more detailed analysis of LINQ performance see Rico's blog:

http://blogs.msdn.com/ricom/archive/...q-linq-to-sql-
performance-part-1.aspx

http://blogs.msdn.com/ricom/archive/...q-linq-to-sql-
performance-part-2.aspx

http://blogs.msdn.com/ricom/archive/...q-linq-to-sql-
performance-part-3.aspx

http://blogs.msdn.com/ricom/archive/...q-linq-to-sql-
performance-part-4.aspx

http://blogs.msdn.com/ricom/archive/...q-linq-to-sql-
performance-part-5.aspx

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[DSK Chakravarthy]

Jon,

Thanks a lot for your reply. Please follow the steps to reproduce the
*complete* program

Step1: Create a windows Application
Step2: Drag a GridView on the windows form
Step3: As mentioned by Amanda, copy the mentioned code onto the Click event
of GridView

Finally, you have the both code snippets. I've taken 2 different windows
applications to run tme individually.

Hope am clear at this, ping me back if am missing some thing.

"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..

Chakravarthy <ds******@india.comwrote:

>Yes, what you said is correct from the point of statements given by the
representatives as well as by the company, Microsoft's official barriers.
But
unfortunately, the figures doesn't lie.

Benchmarks can very, very easily be wrong. Benchmarking is really quite
tricky to get right.

>Am really surprised to see such kind
of figures specially using the latest framework version.

Secondly, i guess there is nothing wrong in the SQL Query. Correct me if
am
found fault.

You haven't told us what the query generated by LINQ is. That's what I
was asking before.

If you could produce a short but *complete* program, we could test it
for ourselves, of course.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

On Sep 4, 2:58 pm, "DSK Chakravarthy" <[e-mail]:

Thanks a lot for your reply. Please follow the steps to reproduce the
*complete* program

Step1: Create a windows Application
Step2: Drag a GridView on the windows form
Step3: As mentioned by Amanda, copy the mentioned code onto the Click event
of GridView

Finally, you have the both code snippets. I've taken 2 different windows
applications to run tme individually.

Hope am clear at this, ping me back if am missing some thing.

It would be far better if you'd just post some code we can compile and
run.

See http://pobox.com/~skeet/csharp/complete.html

Jon

[Jon Skeet [C# MVP]]

Chakravarthy <ds******@india.comwrote:

<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 - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too