Below...
On Wed, 2009-09-09 at 23:11 -0700, greyman wrote:
> I have DbLinq successfully bedded down in my application and now need
> to reduce its CPU usage. To that end I've run some very quick and
> dirty performance profiling which points fairly blatanly to the DbLinq
> query cache as being a good way to do that.
I'll disagree here. It points to DbLinq being slow, and to the query
cache being an improvement, but 2-3x slower than a pure SQL query (using
the query cache) is still not ideal.
Especially when you consider that .NET LINQ-to-SQL using CompiledQuery
is 93.06% the performance of a pure SQL query (contrasted with 33%-50%
the performance, which a 2-3x slower invocation would create):
http://blogs.msdn.com/ricom/archive/2007/07/05/dlinq-linq-to-sql-performance-part-4.aspx
I'm lobbying for CompiledQuery support (as I've suggested before; check
the archives).
(Now if only I could find time to implement it...)
- Jon
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---
