Does connection pooling work fine to execute 60 DB queries to load a page?
Posted
by
willem
on Programmers
See other posts from Programmers
or by willem
Published on 2012-07-01T10:27:39Z
Indexed on
2012/07/01
15:23 UTC
Read the original article
Hit count: 256
We use Linq2Sql in an ASP.NET application. Unfortunately the eager-loading in Linq2Sql isn't as powerful as in Entity Framework, so a lot of the data has to be lazy loaded as needed.
Taking connection pooling into account, is it OK for a web page to execute 60 queries to load a page? Executing a single big query probably won't be much better, as those 60 queries will all those connection pooled connections and not open a new connection each time (which I realize is slow).
Any thoughts?
© Programmers or respective owner
