ASP.NET Website & Entity Framework in seperate thread / multiple threads

Threading is almost never a "magic switch". Apps typically have to be written to be multi-threaded, and trying to force a single-threaded app to be multi-threaded is a recipe for catastrophe.

I'm not even sure what you hope to gain by being multi-threaded. The objects still have to be materialized on a single thread, whether it's your main thread or a worker thread it still takes the same amount of time.

SQL Profiling is a necessary step in the process of using EF for anything but trivial queries.

( restriction in amount of links for new users - therefore multipart answer )

Performance (in general)

some guideance

1. MSDN Performance Considerations
2. P&P Chapter 6 — Improving ASP.NET Performance

1 - Wich in turn links to "Exploring the Performance of the ADO.NET Entity Framework" that explains several options like compiled queries, lazy loading, no tracking etc.

2 - General aproaches like multitude of built in caching options (perhaps? that is in some degree elegant enough) and ways of working with threads.

ASP.NET

Maximizing Performance with the Entity Framework in an ASP.NET Web Application - http://www.asp.net/web-forms/tutorials/continuing-with-ef/maximizing-performance-with-the-entity-framework-in-an-asp-net-web-application

explains several options and ways of analyzing the generated queries

Entity Framework FAQ - http://www.ef-faq.org/objectcontext.html see 3.2. What is the recommendation for running a multithreaded application on the Entity Framework? Is the Entity Framework thread-safe? :

The Entity Framework, like most of the rest of the .NET framework, is by and large NOT thread-safe. So if you want to interact with the Entity Framework or your entity classes from multiple threads, then you must pay careful attention to concurrency issues. One simple model that works for some cases is for each thread to maintain its own context so that no locking is required. This means, of course, that the interactions between the threads must be quite limited (for instance you can't pass an entity from one thread to another without being very careful), but you can do some useful things in spite of these restriction. You could, for example, retrieve data on one thread by using MergeOption.NoTracking, and then divide the data into groups and hand it off to other threads that attach the entities to their own thread context, make updates, and then save.

You could also have one thread for all of your database interactions and send entities over to other threads for processing and back to the database thread for a save. In this scenario, make sure the entities are detached from the context any time they are updated on the other threads or else you will end up with race conditions as the state manager works to keep track of all those changes and therefore is implicitly used from multiple threads simultaneously.

For your theoretical question(s)

1. possible to run the entity framework project (the dll) in another thread then the website

yes : by handling query materilization in another project like in a N-tier application and sending the filled objects from project B to project A; more info

N-tier application - http://msdn.microsoft.com/en-us/magazine/ee321569.aspx

Building N-Tier Apps with EF4 - http://msdn.microsoft.com/en-us/magazine/ee335715.aspx

2 run the database worker (the dll) multiple times "yes", same answer as 1.

//Hope this helps.

You might consider replacing EF with a Micro-ORM such as Dapper-Dot-Net, which is much faster. You can find plenty of info on Dapper right on this site.