Skip to main content
LINQ is an abbreviation and should be spelled with big letters. And fixed a typo.
Source Link
Stu Pegg
  • 4.6k
  • 7
  • 49
  • 91

So

LINQ is a front end tooto CAML so of course CAML is faster, and CAML is a front end tooto SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a sharepointSharePoint site.

I was thinking of processing several huge lists with each on 5 seperateseparate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/

So

LINQ is a front end too CAML so of course CAML is faster and CAML is a front end too SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a sharepoint site.

I was thinking of processing several huge lists with each on 5 seperate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/

So

LINQ is a front end to CAML so of course CAML is faster, and CAML is a front end to SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a SharePoint site.

I was thinking of processing several huge lists with each on 5 separate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/

LINQ is an abbreviation and should be spelled with big letters. And fixed a typo.
Source Link

So

Linq idLINQ is a front end too CAML so of course CAML is faster and CAML is a front end too SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a sharepoint site.

I was thinking of processing several huge lists with each on 5 seperate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/

So

Linq id a front end too CAML so of course CAML is faster and CAML is a front end too SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a sharepoint site.

I was thinking of processing several huge lists with each on 5 seperate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/

So

LINQ is a front end too CAML so of course CAML is faster and CAML is a front end too SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a sharepoint site.

I was thinking of processing several huge lists with each on 5 seperate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/

Tweeted twitter.com/#!/StackSharePoint/status/237972260793749505
Source Link
Hugh Wood
  • 6.3k
  • 1
  • 27
  • 45

CAML vs LINQ vs SQL

So

Linq id a front end too CAML so of course CAML is faster and CAML is a front end too SQL so of course SQL is faster.

However what would be a good test to see where and when to use each of these on a sharepoint site.

I was thinking of processing several huge lists with each on 5 seperate pages and using a performance monitor.

But this doesn't seem like the best option, any ideas? Or does someone know what the real overheads are:

This is what I have found so far (Oh and my boss insists LINQ is faster than CAML I have to prove him wrong!)

http://blog.metrostarsystems.com/2011/10/25/linq-to-sharepoint-vs-caml-vs-sql-performance/