Reputation: 44285
Will putting all my tables in a single edmx significantly harm performance? I have heard this is a bad practice, but this was before entity implemented lazy load. So, now that we have entity 4, is it a non-issue?
I plan to abstract my Models by extending the partial classes of each generated entity, implementing ICrud<ConcreteModel>
. This, combined with MVC3 should nullify any coupling concerns.
Upvotes: 6
Views: 1961
Reputation: 33206
Yes, it does hurt the performance. Performance Issues in Metadata Load Times and in View Generation are the results of a big EDMX model.
Take a look at this post where I discussed this matter at length:
Entity Framework 4: Does it make sense to create a single diagram for all entities?
Upvotes: 3