Entity framework - all tables in a single edmx file

Question

Will all my tables put in one edmx significantly harm performance? I heard that this is bad practice, but that was before the entity realized the lazy load. So now that we have entity 4, is that not a problem?

I plan to abstract my Models by extending the partial classes of each generated object, implementing ICrud<ConcreteModel> . This, combined with MVC3, should eliminate any communication problems.

Answer 1

Yes, it will hurt performance. Performance issues in Metadata Upload Time and Generation View are the results of the large EDMX model.

Take a look at this post where I discussed this question in detail:

Entity Framework 4: Does it make sense to create a single diagram for all objects?