Entity Framework - Model object reuse performance?
LINQ
1
Posts
1
Posters
2
Views
1
Watching
-
What is the best practice with the Entity framework entity model object? Should I cache it in a factory object for subsequent calls or is it inexpensive enough to create per method? For example, I have a factory that has a few calls that are often hit several times during an ASP.Net page load. Should I share the entity model or initialize a new one per hit? Not talking nanoseconds here, just practical performance.
“I have no special talents. I am only passionately curious.” - Albert Einstein