468,241 Members | 1,529 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,241 developers. It's quick & easy.

performance in LINQ

ck1
Hi at all - I want to know if there are diffirence with
Liqn to SQL and Linq To entity performance.

I have read many article on the web that say that Linq To Entity
is more fast than Linq To Sql.

What is your experience about that ?

ck1;
Aug 31 '08 #1
5 1474
ck1 presented the following explanation :
Hi at all - I want to know if there are diffirence with
Liqn to SQL and Linq To entity performance.

I have read many article on the web that say that Linq To Entity
is more fast than Linq To Sql.

What is your experience about that ?

ck1;
I don't have any experience yet, but it doesn't surprise me: Linq to
SQL calls the database, which is much slower than in-memory calls
(which Linq to objects does).

Hans Kesting
Sep 1 '08 #2
On Sep 1, 2:48*pm, Hans Kesting <news.han...@spamgourmet.comwrote:
ck1 presented the following explanation :
Hi at all - I want to know if there are diffirence with
Liqn to SQL and Linq To entity performance.
I have read many article on the web that say that Linq To Entity
is more fast than Linq To Sql.
What is your experience about that ?

I don't have any experience yet, but it doesn't surprise me: Linq to
SQL calls the database, which is much slower than in-memory calls
(which Linq to objects does).
Note that the OP is talking about LINQ to Entities, aka the Entity
Framework - much more directly comparable to LINQ to SQL than LINQ to
Objects is.

Personally I think the difference between LINQ to SQL and the EF is
likely to very much depend on exactly what you're doing. A general
statement is likely to be wrong for a great number of situations.

Jon
Sep 1 '08 #3
ck1
basically i need to create a little Web application:
it's like a blog.

So i think that i can see 1000-2000 users,
every user can have 300 message in 1 year.

I have no complex relation, but very amouth
of query (insert, select).

What i have see is that Entity Framework
isn't serializzable very well. Linq To SQL
have better serializzation.

I suspect that Entity Framework is great
but more great for little application
like website, forum, blog, etc, where linq to sql
it's so better.

But i haven't used so well Entity Framework for say
that... any help ?

ck1;
Sep 1 '08 #4
ck1 <ck****@iol.comwrote:
basically i need to create a little Web application:
it's like a blog.

So i think that i can see 1000-2000 users,
every user can have 300 message in 1 year.
In that case do you really care about the performance? That's likely to
be a pretty tiny database - I doubt that you'll have issues using
either LINQ to SQL or the Entity Framework.

I've used LINQ to SQL for csharpindepth.com - partly because EF wasn't
out when I wrote it - and found it very easy. I believe EF is a more
"enterprisey" solution, but it's probably worth learning both in the
long run.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon.skeet
C# in Depth: http://csharpindepth.com
Sep 1 '08 #5
ck1" <ck****@iol.comwrote in message
news:ew**************@TK2MSFTNGP04.phx.gbl...

What i have see is that Entity Framework
isn't serializzable very well. Linq To SQL
have better serializzation.
What do you mean by "better serialization"? No meaning I can think of makes
any sense in this context.
Sep 2 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by =?Utf-8?B?V2lsc29uIEMuSy4gTmc=?= | last post: by
2 posts views Thread by SC | last post: by
reply views Thread by John Smith | last post: by
2 posts views Thread by AAAAA | last post: by
9 posts views Thread by =?Utf-8?B?cmF1bGF2aQ==?= | last post: by
reply views Thread by =?Utf-8?B?SHlwZXJjb2Rlcg==?= | last post: by
4 posts views Thread by =?Utf-8?B?RXJpYyBGYWxza2Vu?= | last post: by
3 posts views Thread by =?Utf-8?B?UGF1bCBQcmV3ZXR0?= | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.