The script . We currently have a website and are working on creating several websites with an admin website. We use asp.net-mvc, SQL Server 2005, and Entity Framework 4. So now we have the only solution that has all the websites, and all the websites use the same framework structure. The model currently has over 70 tables and could potentially have a lot more in the future ... about 400?
Questions . Is the Entity Framework model slower as it grows? I read a lot of articles where they say that it is rather slow due to additional display layers, when, compared to ado.net? In addition, we thought about having several models, but it seems like bad practice too, and is LINQ useful when we don't use ORM?
So, we are just wondering how and how all the major websites use this technology, because we achieve good performance when using ORM, for example EF, or they never choose ORM? I also worked on the LINQ to SQL application, which had more than 150 tables, and we were faced with a huge launch penalty, for 15-20 seconds it took 15-20 seconds to respond to the site loading. I am sure that this was associated with the high cost of running LINQ to SQL ORM. Would it be great if someone could share their experiences and thoughts on this? What are the best working methods, and I know that it depends on each application, but if performance is a problem, then what are the best steps to be taken?
source